← AI PulseSep 7, 2026

Wire · news · Multi-source brief

xAI Details Connector Management for Grok Business and Enterprise Teams

xAI has outlined the process for team administrators to provision and manage connectors for Grok Business and Enterprise plans within the cloud console, enabling organizational control over external service access.

By Illumora Editorial

Source · Sep 7, 2026, 10:28 PM · On Illumora · Sep 7, 2026, 10:39 PM

Media from the primary source — shown here so you can stay on Illumora.

Synthesized from multiple allowlisted primaries on the same event. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →xAI Docs — Connector Management | SpaceXAI Docs
Save

xAI has provided documentation on how team administrators can manage connectors for Grok Business and Enterprise teams. This process, conducted within the cloud console, allows organizations to control which external services Grok can access. Team members can then connect their individual accounts to these provisioned services.

Key Points

  • Team admins must add connectors in the cloud console before team members can use them on Grok Business and Enterprise plans.
  • Connector management is accessed by logging into console.x.ai, selecting a team, and navigating to Grok Business → Connectors.
  • Provisioning connectors can be done from a catalog or by adding a custom MCP server.
  • Actions such as adding or removing connectors require team management permissions, typically granted to team admins.
  • After provisioning, admins can configure settings like access controls or allowed sites, or remove connectors entirely.
  • Grok 4.6, a frontier model for coding, agentic tasks, and knowledge work, is available on the xAI API with a 500k context window.

Context

According to xAI, the connector management system ensures that organizations maintain control over the external services their Grok instances can interact with. This administrative oversight is crucial for security and compliance. The documentation also notes that Grok 4.6 supports text and image inputs with text-only output and has no text output limit, with pricing structured by token usage and prompt token thresholds.

Why It Matters

This detailed connector management process provides builders and organizations with granular control over Grok's integration with external services, directly impacting data access and operational security. The availability of Grok 4.6 with its large context window and multimodal input capabilities expands the range of tasks developers can address.

What To Do

  • Log into console.x.ai to access the connectors page and manage team connectors.
  • Review the permissions section to understand the requirements for adding or removing connectors.
  • Consult connector-specific documentation for any additional setup steps required for particular services.
  • Note the pricing structure for Grok 4.6 input, cached input, and output tokens when planning usage.

Keep Exploring

/atlas/**grok**-family