Teams | Collaboration | Customer Service | Project Management

We’ve all been there – toggling between six tabs, copying content from one tool into another, and wondering if anyone actually read the brief. The promise of AI was supposed to fix this. Instead, most teams got a chatbot bolted onto the side of their screen. We think AI should work the way a great teammate does: show up where the work happens, understand what’s going on, and actually move things forward. Not from a separate window. Not after a five-paragraph prompt.

Teams of all stripes have run billions of cross‑functional, multi‑tool workflows on Atlassian. After decades spent helping them plan, build, ship, and do, those same workflows are now lighting up with millions of agentic automations, up 7x in the last six months alone. All signals point to the rise of the AI‑native organization, where humans operate at critical junctures, deciding what matters and why, and agents do more of the execution.

Secure communication at the VS-NfD level is not defined by a single feature. It depends on architectural choices, identity controls and operational discipline working together within a clearly defined scope. This section explains the technical foundations that enable secure digital collaboration in classified environments.

Digital collaboration has become the default way of working across business and government. Messaging, file sharing and real-time coordination are now central to how organizations operate. Yet for a long time, classified communication followed a very different path. For VS-NfD and similar classifications, secure communication traditionally relied on tools designed for a much earlier digital era. Phone calls, basic text messaging and highly constrained systems were often the only approved options.

A growth marketing team builds an intake rule in Asana that handles their repetitive tasks. The rule handles every incoming request: One branch for high priority requests spins up and assigns subtasks so that the team can get straight to work. Another for medium-priority tasks uses AI to summarize the request and suggest next steps. A third routes low-priority requests to the team's backlog with a due date. The rule is complex, and it works beautifully. Then the sales team wants to use it too.

A few weeks ago, we soft-launched the Wire Integrations SDK in Staging and called it Phase 1 - the foundation. Today, we're taking the next step. Phase 2 brings the SDK to production in Wire, and with it, Apps become a properly typed, properly visible part of Wire. With this release, Wire becomes a place where automation lives natively: secure by design, end-to-end encrypted, and built on the protocols our customers trust with their most sensitive conversations. Here's what shipping.

People who use an iPhone look at iMessage a lot every day. They use it times but they only use a small part of what iMessage can really do. The iMessage app looks simple with its bubble but it has a lot of features that are not being used. There are things, like effects and scheduling and privacy controls and editing and some secret tricks that are not well known. Most people who use iMessage do not know about these things. They go undiscovered. The iMessage app is very powerful.