> For the complete documentation index, see [llms.txt](https://docs.spreo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spreo.io/management/security-and-access-control.md).

# Security & Access Control

The ways to control who can join your organization and its boards.

For security purposes, boards are protected by default: only members of a board's team can open it straight away.

New Organizations start with Auto-Join open to every email domain, so set your own domains in [Auto Join](/management/manage-general-account-settings.md#auto-join-settings) to control who can become a member.

You can use the following methods to control access to the Organization Account:

* Restrict who can become a team member by using domain-based access control
* Enable invite approvals. <mark style="background-color:purple;">Enterprise plan only</mark>
* Setup Single Sign-on (SSO). <mark style="background-color:purple;">Business and Enterprise plans only.</mark>
* Invite Guests (external collaborators) to boards. Guest access is restricted to just the board shared with them. <mark style="background-color:purple;">Business and Enterprise plans only.</mark>

### Organization Access

All plans are able to restrict access to the organization and set whitelist joining rules with the [Auto Join](/management/manage-general-account-settings.md#auto-join-settings) setting, or for Business and Enterprise plans through integration with your [Single Sign On](/management/single-sign-on.md) provider.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spreo.io/management/security-and-access-control.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 `build a script that syncs our docs to a CMS` 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.