Teams | Collaboration | Customer Service | Project Management

“What's the difference between our PPO and HDHP?” “Can I add my spouse?” “How much can I contribute to my HSA?” “When is the deadline?” “Did my enrollment actually go through?” As you see, open enrollment creates a predictable surge of questions for HR.

Employee self-service was meant to make HR easier. But in many companies, employees still have to jump between portals, policies, forms, and HR systems just to get one simple thing done. Need to check a leave balance? Find the HRIS. Need a benefits answer? Search SharePoint. Need to know whether a request was approved? Open another system or ask HR. That is self-service, but it still puts a lot of work on the employee. An AI agent for HR changes that experience.

TL;DR When deploying a service on your infrastructure, it can be tempting to just grab open source containers and roll them out with simple tools. Docker compose or ansible playbooks can do a fantastic job at rolling out a few containers in no time. But putting simple services online is the easy bit. The more containers in your stack, the more difficult it becomes to deploy them consistently, and the more chances for it to break.

Tag Cloud metadata fields are meant to make files easier to find, but only if the values in them stay consistent. Left open-ended, they tend to fill up with near-duplicates and typos ("Marketing," "marketing," "Mkt") that quietly undermine search and filtering. Pydio v5.1 gives administrators a way to fix that: you can now define and restrict which values are available in Tag Cloud fields, so users pick from a controlled list instead of typing free text.

“Who the *** changed the plan?!” Pretty realistic for a typical morning on a construction site, isn’t it? A crew shows up ready to work and finds out the plan changed somewhere up in the office, but the information didn’t make it to the field in time. Almost every superintendent, foreman, or project manager has said it, heard it, or dealt with the fallout.

Individual AI adoption has outpaced our ability to redesign how teams actually work together. The numbers back it up. In Forrester’s “The Visual Era of Collaborative Intelligence”, 89% of leaders say improving collaboration is key to hitting their organization’s goals – yet 75% agree most AI tools are built for individual, not team productivity, and 39% say that individual-first bias is actively hurting their AI ROI.

The honest answer is that you cannot know whether someone is working by watching them, and remote work did not create that problem. It removed the illusion that solved it. In an office, presence stood in for productivity. Take the office away and the substitute disappears, leaving a question that was always there. Two things follow. The signals most monitoring tools sell are weak proxies that a determined employee defeats in minutes.

The leaves are turning, and tractor rides aren’t the only thing rolling, new Slack features are too. This month was about less switching, less digging and less manual clean-up. Whether you’re an admin trying to get usage data, a seller trying to keep a CRM record current or a developer building on the Slack MCP server, this drop is about giving you the context that you need right where you already are. This month, we grew a fresh batch of features across AI agents, CRM and mobile.