Bring Grok Bot to work with Merge for Workforce

Grok Bot can now access approved company tools through Merge for Workforce.

Grok Bot gives employees persistent AI teammates that can handle multi-step work across apps and websites. Each Bot has its own memory and access to a cloud computer, so it can keep working after an employee closes the app or shuts their laptop. Employees can also create Team Bots that share the same job, tools, and instructions across a group.

Once a Bot is connected to company systems, that persistence raises the stakes. Access needs to follow the person asking, especially when employees with different roles and permissions use the same Team Bot.

Merge for Workforce provides that control through one governed MCP endpoint. Employees can use personal and Team Bots with approved company tools. IT decides which tools are available, applies security rules to each action, and keeps a record of every call through Merge.

Connect personal and Team Bots to approved company tools

Grok Bot supports custom MCP servers over remote HTTPS and can authenticate each user through OAuth. Point it at Merge for Workforce, and the connection leads to the tools your company has approved.

An employee can connect a personal Bot to Merge once and use that connection across their Bots. For a Team Bot, the owner adds the Workforce connection to the shared setup. Each teammate still signs in with their own account when the Bot needs to act for them, so one employee never inherits another's access.

After an employee signs in through your identity provider, Workforce uses their Groups to determine which tools appear. A salesperson and a finance employee can work with the same Team Bot and receive different tool access based on their roles.

When the Bot requests an action, Merge checks whether the employee can use that tool, then runs it with their credentials and permissions. If the action falls outside the employee's granted tool set, the call fails and appears in Requests for an admin to review.

A team can share one Bot without sharing one set of credentials. Access stays tied to the employee behind each request.

Apply company security rules to every Grok Bot action

A Bot can keep working across several systems after an employee steps away. One bad instruction can travel much farther than it would in a typical assistant session.

Merge checks every tool call against the company's security rules before sending it to a third party. IT and security teams can:

• Detect sensitive data. Identify personal, financial, health, or other regulated information in a tool call.
• Enforce company-specific rules. Catch internal account numbers, project names, or other identifiers using custom rules.
• Evaluate requests in context. Use plain-language guardrails to stop actions involving a confidential project or another topic that should not cross a system boundary.

Depending on the rule, Merge can log the match, redact the sensitive value, or block the action. AI Guardrails can also inspect a tool's response before it returns to Grok Bot.

The rules stay in Merge and apply whenever a personal or Team Bot uses the governed connection. Security teams do not have to recreate them for every Bot an employee makes.

See what employee AI is doing across the organization

A chat history is not an audit trail. Merge records each governed tool call with the employee, tool, status, and request context. IT can see which systems a Bot reached, which actions succeeded or failed, and which security rules fired.

Security and compliance teams can investigate that activity in one place instead of piecing it together from separate application logs. When several employees use the same Team Bot, the record still shows which employee made each governed request.

Merge for Workforce also gives IT a broader view of employee AI use across the organization. IT can see where adoption is already happening and guide employees toward governed connections instead of starting with a company-wide block.

Give Grok Bot a governed path to work

Employees will use both personal AI teammates and shared Team Bots. IT should not have to rebuild identity, access, security, and audit controls for each one.

Merge for Workforce gives both types of Grok Bot a governed path to company tools. Employees keep the persistent agents that fit their work, while IT manages access and security through one connection.

Contact Merge to get access to Grok Bot support in Merge for Workforce.

‍