> 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.](/files/CbhLKjSWSZRdAxQB6EVI)

## 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](/files/wkp3DcikNy7h2B0IjoJB)

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](/dope.console/settings/users/importing-from-google.md).
{% endhint %}

{% hint style="warning" %}
Azure / Microsoft Entra Security Groups are not currently supported for policy assignment and exceptions in dope.console
{% 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 %}

![](/files/dOMlTwfhKssVS18brgrE)

### 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.

![](/files/u9XYdLJ7oggpdQQ2fJmW)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.