Repository Public
1<!-- source: https://docs.x.ai/grok-bot/identity-and-access (from https://docs.x.ai/llms-full.txt, retrieved 2026-09-19T05:28:55Z) -->2#### Manage and protect34# Configure identity and access56This guide is for admins running Okta or Microsoft Entra ID as their identity7provider (IdP). It covers giving people outside your engineering organization8access to Grok Bot through your Cursor team, and letting members sign in to9IdP-provisioned apps from the Bot's computer. For the broader security model,10see [Grok Bot security](/grok-bot/security); for rollout steps and the admin11controls, see12[Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises).1314Grok Bot uses your Cursor account, so there is no separate Grok Bot app in Okta15or Entra ID. Everything in this guide happens on the Cursor app you already16have. Cursor single sign-on is SAML 2.0 and works with Okta, Microsoft Entra,17Google Workspace, and OneLogin; this guide details the two where device-trust18policies most often need attention.1920## What you will change2122You will make two changes, and they do different jobs:2324* [Assign the Cursor app](#assign-the-cursor-app) so users outside your25 engineering organization can access Grok Bot through your Cursor team.26* [Add an authentication rule](#allow-sign-in-to-idp-apps-from-the-computer) so27 users can sign in to IdP-provisioned apps from the Bot's computer, which runs28 Linux and does not run device-trust agents.2930Only the first change controls Grok Bot sign-in. The second never blocks it, and31it does not apply to plugin sign-in, because plugin authentication does not go32through the computer.3334## Before you start3536Grok Bot access requires the user to be a member of your Cursor team. Members37sign in with their Cursor account, so your existing38[Cursor SSO](https://cursor.com/docs/account/teams/sso) applies. With39auto-provisioning on, a user joins the team at first sign-in; otherwise,40provision the user, then have them sign in to Cursor for a seat or invite them41from the [Cursor dashboard](https://cursor.com/dashboard).4243If you use [SCIM](https://cursor.com/docs/account/teams/scim), provisioning is44SCIM 2.0, available on the Enterprise plan, and deprovisioning is automatic:45removing the user in your identity provider removes them from Cursor.4647## Assign the Cursor app4849A user can sign in only if they have a Cursor account, and they get one through50assignment to your existing Cursor SSO app, plus the SCIM app if you use SCIM.51If Cursor is assigned only to engineering, everyone else fails with52**User is not assigned to this application**, or their invite never completes.53Do not create a second Grok Bot application; widen assignment on the Cursor app54you already have.5556### Assign the app in Okta57581. Go to **Admin Console → Applications → Applications** and open your existing59 Cursor app.602. Open **Assignments** and select **Assign → Assign to Groups**. To assign61 individuals instead, select **Assign to People**.623. Add every group that should get Grok Bot, not only engineering.634. If you use SCIM, assign the same groups to the Cursor SCIM app and push them.64 Users appear in Cursor only after they are assigned to the SCIM app.655. Confirm each group is also assigned to the SAML app. SCIM assignment without66 SSO assignment still blocks first sign-in.6768If you use org-level identity in Cursor, map the directory group to the Grok Bot69team after it syncs; see70[Organizations](https://cursor.com/docs/enterprise/organizations). Use separate71groups for app assignment and Group Push.7273### Assign the app in Microsoft Entra ID74751. Go to **Microsoft Entra admin center → Enterprise applications** and open76 your existing Cursor enterprise app.772. Open **Users and groups** and select **Add user/group**.783. Add every group that should get Grok Bot, not only engineering.794. If you use SCIM, assign the same groups to the Cursor provisioning app. Turn80 provisioning on and scope it to assigned users and groups.815. Confirm the assignment grants SSO rather than report-only access.8283Group-based assignment requires Entra ID P1 or P2, and nested groups are not84included. Users must be explicitly assigned, unassigning blocks SSO sign-in, and85with SCIM it also removes them from Cursor.8687For either provider, the assignment works when:8889* A user outside the original engineering assignment can open Grok Bot and90 complete Cursor SSO without **User is not assigned to this application**.91* With auto-provisioning on, that user appears on the Cursor team after first92 sign-in, without a manual invite.93* With auto-provisioning off, that user is on the team after they sign in to94 Cursor for a seat, or after you invite them from the dashboard.9596## Allow sign-in to IdP apps from the computer9798Inside the hosted computer, members sign in to applications through your own99identity provider in the browser, so your session policies govern those100sessions. The computer runs Linux and is not enrolled in mobile device101management (MDM), and device-trust agents like Okta FastPass do not run on it.102Any rule that requires FastPass, a registered or managed device, a compliant103device, or a phishing-resistant factor only FastPass can satisfy fails in the104computer browser.105106Do not turn FastPass or device compliance off for the whole company. Add a107higher-priority rule scoped to this unmanaged Linux session. This change covers108only the IdP-provisioned apps the Bot opens in the computer browser; it is not109required for Grok Bot sign-in or for plugin sign-in.110111These sign-in methods work in the computer browser:112113* Password plus a second factor that works in a remote browser, such as Okta114 Verify push or an authenticator app.115* Passkeys stored in a password manager on the computer, installed with a116 [Team Setup script](/grok-bot/teams-and-enterprises#team-setup). Team Setup117 is Enterprise only.118119> Requiring managed devices for Grok Bot sign-in itself still works. Grok Bot120> uses your Cursor SSO, so a device-aware sign-in policy in your identity121> provider applies to it. That policy gates sign-in on the member's device, not122> the hosted computer.123124### Add the rule in Okta125126In Okta Identity Engine, the computer matches the **Other Desktop** device127platform; there is no Linux checkbox. Repeat these steps for each128IdP-provisioned app the Bot opens in the computer browser.1291301. Go to **Admin Console → Security → Authentication Policies** and open the131 policy attached to the app. To find the policy, open **Applications**, then132 the app, then **Sign On**.1332. Add a rule above the FastPass, managed-device, and deny catch-all rules. Name134 it so you can find it later, for example **Grok Bot computer (Linux)**.1353. In the IF conditions, scope the rule to a group. The Cursor-assigned group136 works if you do not want the rule company-wide.1374. Set **Device platform** to **Other Desktop** and **Device state** to **Any**.138 Do not require **Registered**, **Managed**, or a device assurance policy that139 depends on FastPass.1405. In the THEN conditions, set access to141 **Allowed after successful authentication** with142 **Password + Another factor**. Do not require phishing-resistant or143 hardware-protection factors.1446. Save the rule and confirm it sits above the unmanaged-device deny catch-all.145146If several apps share one FastPass-on-managed-devices policy, add the Linux rule147to the shared policy and scope it by group, or give those apps their own policy.148On Classic Engine, allow **Other Desktop** without requiring149**Device Trust = Trusted**.150151### Add the policy in Microsoft Entra ID152153Entra ID has no FastPass. The grants that block the computer browser are a154compliant device, a hybrid joined device, a phishing-resistant authentication155strength that only a platform or managed passkey can meet, and an approved156client app or app protection policy.1571581. Go to159 **Microsoft Entra admin center → Protection → Conditional Access → Policies**.1602. Find every policy that applies those grants to the IdP apps the Bot needs.1613. Leave those policies on. Add a higher-priority policy for Grok Bot users on162 Linux, or exclude them from the blocking policies.1634. In the new policy, set the users to the Cursor-assigned group and target the164 IdP apps they must open on the computer. Select **All resources** only if you165 accept that scope.1665. Under **Device platforms**, include **Linux** and exclude **Windows** and167 **macOS**.1686. Set the grant to **Require multifactor authentication** only.1697. Start the policy in report-only mode, then turn it on.1708. On existing compliant-device policies, exclude the group or exclude Linux.171172For phishing resistance without a managed device, use an authentication173strength a synced passkey can satisfy, and test sign-in from the computer before174enforcing it.175176For either provider, the change works when a user can sign in to177IdP-provisioned apps from the Bot's computer without a FastPass or178device-compliance error, plugin sign-in works as before, and laptop sign-ins are179unchanged.180181Revocation stays with you either way: revoking the user in your identity182provider ends their in-computer application sessions, and an organization admin183can [terminate the member's computer](/grok-bot/security#identity-and-sign-ins)184at any time.185186## Limitations187188* Okta FastPass does not run on Linux, so the Bot's computer cannot satisfy189 FastPass or managed-device rules.190* The computer is not enrolled in MDM by default.191* Group-based assignment in Entra ID requires P1 or P2 and does not include192 nested groups.193194## FAQ195196### Do I need a separate Grok Bot app in Okta or Entra ID?197198No. Grok Bot sign-in uses the Cursor account, so your existing Cursor app199controls access. Widen assignment on that app instead of creating a new one.200201### Does the device-trust change affect plugin sign-in?202203No. Plugin authentication does not go through the computer, so authentication204rules for the computer browser do not apply to it.205206### Will these changes weaken sign-in on employee laptops?207208No. Scope the new rule or policy to the Linux platform and the Cursor-assigned209group, and laptop sign-ins keep your existing requirements.210211### If I unassign a user from the Cursor app, do they lose access?212213Yes, they can no longer sign in through SSO. With SCIM, unassigning also removes214them from Cursor automatically; without SCIM, remove them from the team in the215dashboard.216217## Related pages218219* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)220* [Grok Bot security](/grok-bot/security)221* [Connect to private networks](/grok-bot/private-networks)222* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)223* [SSO](https://cursor.com/docs/account/teams/sso)224* [SCIM](https://cursor.com/docs/account/teams/scim)225* [Organizations](https://cursor.com/docs/enterprise/organizations)226