LoginSign Up
← Back to all sparks
M

Mattermost

COLLAB
Velocity5.0

Open-source secure collaboration platform for technical teams.

mattermost.com ↗

Attribute-based access control keeps climbing a layer per release; the AI agents get failure handling.

abacaccess controlai agentszero trustdata sovereigntyregulated deployments
◆Current state
Mattermost ships a v11.x release roughly monthly and each one pushes attribute-based access control one layer further out: v11.9 took ABAC to channel-level policies, v11.10 takes it to team membership and lets admins write policies against native user attributes instead of standing up an identity integration first. Between releases the feed is almost entirely thought-leadership aimed at defense and regulated buyers - zero trust, air-gapped networks, data sovereignty. The AI agent work has moved past capability into reliability, with dynamic tool calling, on-demand file context, and automatic fallback when a model goes down.
◆Where it's heading
The ABAC arc is the spine of this product right now, and it is being built outward from a single policy engine rather than bolted onto each surface separately - channels, then teams, then the attribute source itself. Dropping the integration requirement for user attributes is the tell: Mattermost wants ABAC to be configurable by an admin in an afternoon, not a deployment project. The agent features are converging on the same buyer, since a model that silently fails is not deployable in the environments this release notes are written for.
◆Prediction
The next release most likely extends ABAC to a further object - playbooks, boards, or integrations - or adds policy simulation and audit tooling, since admins writing policies across three scopes now need a way to see what a rule will actually block before it blocks it.

◆Recent moves

  1. 4d ago

    Mattermost v11.10: Team ABAC Membership, Native User Attributes in ABAC, AI Agent Enhancements & More

    v11.10 extends ABAC governance from channels to team membership and lets policies read native user attributes without a separate identity integration, which removes the main setup cost of the feature. The AI agents pick up dynamic tool calling, on-demand file context, and automatic model fallback. It is the next step in an arc already underway rather than a change of direction.

    View source ↗
  2. 8d ago

    What Is an Air-Gapped Network?

    An explainer on air-gapped networks, part of the steady stream of content aimed at the defense and regulated buyers the ABAC work targets. No product change.

    View source ↗
  3. 11d ago

    Your Teams Are Already Translating Sensitive Data. The Question Is Where It Goes.

    Marketing commentary on where sensitive data goes when teams use outside translation tools. It frames the data-residency argument behind the sovereignty positioning but ships nothing.

    View source ↗
  4. 15d ago

    The Collaboration Gap in Zero Trust: Why Sovereignty Can’t Stop at the Perimeter

    A zero-trust positioning post arguing that perimeter controls stop short of the collaboration layer - the same argument the ABAC releases are the product answer to. No shipped change.

    View source ↗
  5. 20d ago

    Agentic AI for Mission-Critical Operations: What Enterprise Leaders Need to Know

    An executive-audience piece on agentic AI in mission-critical operations. It sets up the reliability framing that the v11.10 agent fallback work delivers against, but it is content, not a release.

    View source ↗
  6. 28d ago

    Secure Mobile Collaboration: How Federal & Private Organizations Can Protect Mobile Data at Scale

    A guide to protecting mobile collaboration data at scale for federal and private organizations. Same audience as the ABAC track, no product change attached.

    View source ↗