> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/dashboard/administration/email-domain-based-access.md).

# Email Domain Based Access

Domain binding allows users to automatically join your Currents organization based on their email domains. When signing up to Currents platform, they will automatically become team members if their email domain matches.

You can allow users with your company email domain to connect to your Currents organization by activating this option in the onboarding screen.

<figure><img src="/files/vWr1MeX31fH56plkaafF" alt=""><figcaption><p>Enabling Domain Access via Currents onboarding form</p></figcaption></figure>

You can also request to activate this feature by entering the members' administration panel in Currents dashboard. You can have multiple domains enabled for the organization.<br>

<div data-full-width="false"><figure><img src="/files/GnkEOC0h0X2RGzEIBdQf" alt=""><figcaption><p>Enabling Domain Access via Currents Team Management view</p></figcaption></figure></div>


---

# 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://docs.currents.dev/dashboard/administration/email-domain-based-access.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.