Skip to main content

Users and API clients

This local console is not CrowdStrike production. Users and API clients you create stay on this clone. They do not provision a Falcon tenant and they do not call CrowdStrike production.

Sign in first. Follow Signing in to the console with [email protected], then use the left rail.

Users​

Choose Users in the rail. The table lists console users for this CID (email, name, and role). The seed administrator is [email protected]. Leave the filter empty to see everyone.

Type this Falcon Query Language (FQL) filter and apply it to match the seed analyst:

email:'analyst*'

An empty filter lists all users. A filter that is not valid FQL shows an error on the list. No users matching the filter shows an empty list.

Create a user​

  1. Choose Create user.
  2. Fill in Email, First name, Last name, Password, and a role (Falcon Analyst or Falcon Administrator).
  3. Submit.

The new user can sign in on the console sign-in page with that email and password. A duplicate email stays on the form with an error.

Delete a user​

You can delete a user that is not the last Falcon Administrator. You cannot delete the last administrator — including the seed analyst while they are the only administrator. That delete is refused.

API credentials​

Choose API credentials in the rail. The table lists API clients for this CID, including the seeded clients cs-local-read and cs-local-hosts. Secrets are not shown on the list.

Create a client​

  1. Choose Create client.
  2. Optionally enter a Name.
  3. Select one or more scopes (user-management:read, user-management:write, hosts:read, alerts:read, alerts:write, host-groups:read, host-groups:write, sensors:read, installation-tokens:read, installation-tokens:write, prevention-policies:read, prevention-policies:write, response-policies:read, response-policies:write, sensor-update-policies:read, sensor-update-policies:write, device-control-policies:read, device-control-policies:write, ioc:read, ioc:write, custom-ioa:read, custom-ioa:write, api-clients:read, api-clients:write).
  4. Submit.

The client secret is shown once. Copy it before you leave that screen. The console does not show the secret again.

Reset a secret​

Choose Reset on a client. A new secret is shown once. Tokens minted with the old secret stop working.

Scopes on a client control what a Bearer token from that client can call. They do not replace the console session you already have after sign-in.