Customer may let Users use Grok Bot for internal business purposes and must configure its controls
Subject to the Agreement, the Provider’s acceptable use policy, and the applicable account settings and permissions, Customer may permit its Users to use Grok Bot for Customer’s internal business purposes. Customer is responsible for configuring and administering the available settings, permissions, approval requirements, integrations and usage limits. Which controls are available may depend on Customer’s plan, configuration and deployment.
Details
Who
Customer, through its Users
Why
Customer’s internal business purposes
Condition
Subject to the Agreement, acceptable use policy, account settings and permissions
Supporting quotations
Subject to the Agreement, the Provider’s acceptable use policy, and the applicable account settings and permissions, Customer may permit its Users to access and use Grok Bot for Customer’s internal business purposes.
Customer is responsible for configuring and administering available settings, permissions, approval requirements, integrations, and usage limits.
Available controls may depend on Customer’s plan, configuration, and deployment.
Qualifications & exceptions
Use is permitted for Customer’s “internal business purposes.”
Subject to the Agreement, the acceptable use policy, and applicable account settings and permissions.
Available controls may depend on plan, configuration and deployment.
Not stated here
The definition of Customer covers an individual using Grok Bot on their own behalf, but this section speaks only of internal business purposes; it does not say whether or how personal use by an individual is covered.
Which controls exist on which plan or deployment is not stated here.
Account & Service Control · Permission or license
Customer authorizes agentic actions it requests, approves, configures or permits, including ones Grok Bot starts itself
Customer authorizes Agentic Actions that Customer or its Users request, approve, configure or permit. That includes Agentic Actions that Grok Bot starts on its own, as long as they are within the scope of access, permissions and authority that Customer or its Users have granted.
Details
Who
Customer and its Users
Condition
Within the scope of access, permissions and authority granted by Customer or its Users
Supporting quotations
Customer authorizes Agentic Actions requested, approved, configured, or permitted by Customer or its Users, including Agentic Actions that Grok Bot initiates autonomously within the scope of access, permissions, and authority granted by Customer or its Users.
Qualifications & exceptions
Autonomous actions are covered only “within the scope of access, permissions, and authority granted by Customer or its Users.”
Not stated here
This sentence does not say what happens when Grok Bot acts outside the scope that was granted; a later all-capitals paragraph assigns responsibility for actions “whether or not” Customer authorized them.
Cross-references
contrast (model-proposed): Customer is responsible for all Grok Bot actions, even ones it did not intend or authorize — Section 2.2 ties Customer’s authorization to actions it requested, approved, configured or permitted, or that Grok Bot started within the access Customer granted. The all-capitals paragraph makes Customer solely responsible for all Agentic Actions taken by Grok Bot whether or not Customer intended, anticipated or authorized them. The document does not say how the two fit together.
Account & Service Control · Restriction or exception
Customer will use appropriate human review before permitting agentic actions
Customer will use appropriate human review before permitting Agentic Actions, including those involving external communications, financial transactions, data deletion, permission changes, production systems, legal commitments, or material effects on third parties.
Details
Who
Customer
Condition
Before permitting Agentic Actions, especially external communications, financial transactions, data deletion, permission changes, production systems, legal commitments or material effects on third parties
Supporting quotations
Customer will use appropriate human review before permitting Agentic Actions, including those involving external communications, financial transactions, data deletion, permission changes, production systems, legal commitments, or material effects on third parties.
Qualifications & exceptions
The listed kinds of actions are introduced by “including,” so they are examples rather than a closed list.
Not stated here
“Appropriate” human review is not defined.
This paragraph has no number; it follows section 2.3 and precedes 2.4, and the document does not say which section it belongs to.