Overview
The Clarity CrowdStrike Falcon connector reads who has access to your Falcon console and with which roles, for user access reviews. It uses the Falcon user-management API. It is read-only: Clarity never creates, changes or removes anything in Falcon.
What Clarity syncs | Falcon source | Direction |
|---|---|---|
Users (internal and external) |
| read |
Roles (built-in and custom) |
| read |
Each user’s effective role grants, both direct and through a user group |
| read |
Each role’s permissions (see the note below) |
| read |
Connection test |
| read |
Authentication is OAuth 2.0 client credentials, using a Falcon API client (a client ID and secret). There is no browser sign-in or consent step. Clarity requests a short-lived token from your cloud’s /oauth2/token endpoint and renews it automatically.
Status note: Clarity treats a user whose Falcon status is active as active. Every other status, for example a pending invitation, is imported as inactive.
Role permissions note:
CrowdStrike does not publicly document the two role-permission endpoints. If your tenant does not serve them, or your API client is not allowed to call them, Clarity still imports users, roles and role grants. It logs a warning and skips only the per-role permission detail.
Prerequisites
A Falcon user with the Falcon Administrator role. Only administrators can see the Client Management page and create API clients.
Knowledge of which Falcon cloud your tenant is on (Step 1).
MSSP / Flight Control customers only: the child CID of each customer tenant you want to review (Step 3).
Step 1 — Identify your Falcon cloud
Every Falcon tenant lives on one cloud, and the API only answers on that cloud’s host. The Base URL is the most reliable way to tell which cloud you are on. Falcon shows it at the top of the API clients tab (Step 2), and again when you create the API client.
Clarity Falcon Cloud option | API host Clarity calls |
|---|---|
US-1 (default) | api.crowdstrike.com |
US-2 | api.us-2.crowdstrike.com |
US-3 | api.us-3.crowdstrike.com |
EU-1 | api.eu-1.crowdstrike.com |
US-GOV-1 | api.laggar.gcw.crowdstrike.com |
US-GOV-2 | api.us-gov-2.crowdstrike.mil |
The console address (for example falcon.us-2.crowdstrike.com) usually matches the cloud, but sign-in links can point at falcon.crowdstrike.com for tenants on other clouds. When in doubt, use the API client’s Base URL.
Step 2 — Create an API client for Clarity
Sign in to the Falcon console with an account that has the Falcon Administrator role.
Open the menu (top left) and go to Support and resources → Resources and tools → Client Management.

Falcon menu: Support and resources > Resources and tools > Client Management
Open the API clients tab (not MCP clients), then choose to add a new API client.
Name it something recognizable, for example Clarity Connector.
In the Access Scopes list, find the User management row and tick Read. Leave its Write box, and every other row, unticked. Clarity does not need API Client Management or any other scope. Typing user in the scope search box filters the list down to this row.

Click Create, then copy the Client ID, the Secret and the Base URL from the confirmation dialog.
Falcon API Secret
Falcon shows the Secret only once. If you lose it, reset the secret on the API client and update Clarity.
Don’t see Client Management? The entry is shown only to users with the Falcon Administrator role. Without that role, Resources and tools lists only items such as Notifications, Tool downloads, Sitemap and Falcon status. Ask a Falcon Administrator to create the API client, or to grant you the role. Older consoles call the page API clients and keys and list it under Support → API Clients and Keys. If your menu is laid out differently, open Resources and tools → Sitemap and search for “API clients”.
Use a dedicated API client. Falcon rate-limits each API client against one shared request budget. If you share the client with another integration, one can slow the other down.
IP restrictions. Clarity cannot provide a fixed set of IP addresses to allowlist. If your Falcon tenant restricts API access to allowlisted IP addresses, remove that restriction for the Clarity API client before you test the connection.
Step 3 — MSSP (Flight Control) only: find the child CID
Skip this step for a normal, single-tenant Falcon account.
If you are an MSSP using Falcon Flight Control and you created the API client in the parent CID, Clarity can act on one child CID through it. Add one Clarity integration per child CID you want to review, each with the same client ID and secret, and set Member CID to that child’s CID.
Child CIDs are listed in Flight Control's child-CID management view.
Step 4 — Enter the credentials in Clarity
In Clarity, add a new CrowdStrike Falcon integration and fill in these fields.
Clarity field | Required | Value |
|---|---|---|
Falcon Cloud | Yes | Your cloud from Step 1, chosen from the drop-down. Defaults to US-1. |
API Client ID | Yes | The API client’s Client ID from Step 2. |
API Client Secret | Yes | The API client’s Secret from Step 2. The field is masked and the value is stored encrypted. |
Member CID (MSSP only) | No | MSSP parent API clients only: the child CID from Step 3. Leave it blank for a single-tenant account. |
Click Next to save and then test the credentials. The test requests a token and then reads one user, so a pass confirms the cloud, the credentials and the User management: Read scope together.

Step 5 — Run the first sync
On the application page, click Sync. When the sync finishes, the Sync Log tab shows a Completed row with the entitlement, user and user-entitlement counts.

The Entitlements tab lists each Falcon role as an entitlement of type Role, alongside the application’s base entitlement.

Troubleshooting
Symptom | Likely cause |
|---|---|
Client Management is missing from Support and resources → Resources and tools | Your Falcon user does not have the Falcon Administrator role. Have a Falcon Administrator create the API client (Step 2). |
Test fails with “issued an API token but rejected it on the first API call (HTTP 401)” | Falcon Cloud is wrong. Falcon issues a token on any cloud but rejects it on every call except its own. Pick the cloud that matches the API client’s Base URL. |
Test fails with “not allowed to read users (HTTP 403)” | The API client is missing the User management: Read scope. Edit the API client and add it. |
Test fails with a generic credentials error | The client ID or secret is wrong, or the secret was reset. If both are correct, an IP restriction on your tenant may be blocking Clarity. Remove the restriction (see Step 2). |
Test fails with “user-management API was not found on this cloud (HTTP 404)” | Check Falcon Cloud first. If the cloud is correct, your cloud may not yet serve the newer user-management API version; contact Clarity support. |
Sync succeeds but roles have no permission detail | Your tenant does not serve, or your API client may not read, the role-permission endpoints. Users, roles and grants are still imported. A warning is logged. |
An MSSP child’s users don’t appear | Member CID is blank or names the wrong child CID, or the API client was created in the child CID instead of the parent. |
Sync is slow on a large tenant | Expected: Falcon only returns role grants one user at a time. Make sure no other integration shares the API client’s rate-limit budget. |
What Clarity does NOT do
No writes. Clarity never creates, deletes or edits Falcon users. It does not grant or revoke roles, or reset passwords or 2FA, even though the Falcon API supports some of these.
Not a source of truth. Falcon user records are not used to create or update Clarity identities’ HR attributes.
No role or user-group management. Clarity reads roles and the user groups that grant them. It does not create or change roles, user groups or permissions.
No Flight Control hierarchy (yet). Clarity does not read MSSP CID groups, MSSP user groups or the parent-to-child role links. Each child CID is reviewed as its own integration.
No security data. Clarity does not read detections, hosts, policies or any other Falcon product data. It works only with console users and their access.
Need Help?
If you have any problems, contact your customer success team. You can also get in touch with our general support via email, open a support ticket. Our general support team is available Monday - Friday from 8:00 AM - 6:30 PM CST.