> For the complete documentation index, see [llms.txt](https://inflight.dope.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inflight.dope.security/introducing-dope.swg/quick-start-guide/import-user-and-group-data.md).

# Import User and Group Data

While dope.swg can be used without importing user and group data, admins must import user and group data to fully utilize the product.

## dope.console

![When you open the dope.console, you’ll arrive at the dope.swg overview dashboard.](https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2FcYP3DGq7jL5KMHk3SmLl%2Fgitbook-2023_14.png?alt=media\&token=a79dc303-0a22-4cbe-be36-5fcd2d74cf6b)

## Endpoint Auth & User Import

First, enable endpoint authentication. This forces users to authenticate with their corporate emails and automatically have the correct web security policy applied. By using an integration with Microsoft 365 and Google, it’s a click without any SAML configuration.

![Click to enable endpoint authentication](https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2F731CaiMi1FR4Ds0EZefe%2Fgitbook-2023_15.png?alt=media\&token=76969a31-4e77-439e-b0f6-45df7aef46cf)

In other words, if you're using Okta, Ping, or another 3rd-party IDP, you'll automatically redirect to that IDP.

Now, use the link provided to authorize access to the users and groups.

{% hint style="info" %}
Only Google/Microsoft 365 admins can authorize users and group imports. This link can be copied and sent to them. Google import requires special authorization [detailed here](https://inflight.dope.security/dope.console/settings/users/importing-from-google.md).
{% endhint %}

{% hint style="info" %}
Microsoft 365 Groups and Microsoft Entra security groups are supported for policy assignment and exceptions. This includes security groups synchronized from on-premises Active Directory.
{% endhint %}

Once the admin has authenticated with either Google or Microsoft 365, the dope.security console will import your users and groups. Any updates to groups or new users in either Google or Microsoft 365 are synced and reflected in the dope.swg console.

{% hint style="danger" %}
Without importing users and groups into the console, functionality will be limited:

* No Custom Policies
* No Policy Exceptions
* Limited Analytics Functionality
  {% endhint %}

![](https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2F4HRegaBRiEocWn7V0ubX%2Fgitbook-2023_16.png?alt=media\&token=66d3ac44-cc41-4553-b914-a1dec95b8984)

### Acceptable Domains

If your company uses multiple domain names, enter the different domain names that may be used by users.

Logins from other domains will be blocked.

{% hint style="success" %}
Add comma-separated domain names, e.g. for <user@voyager.com>, just put in “voyager.com”.
{% endhint %}

Once you’ve completed adding domains, select ‘Save’ on the bottom right panel to save your changes.

![](https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2F0o8PKENn2Pq18OAeSNGT%2Fgitbook-screenshots_16.png?alt=media\&token=a97ed583-b913-4e0e-a86b-a9525b43eaa4)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://inflight.dope.security/introducing-dope.swg/quick-start-guide/import-user-and-group-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
