> 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

For security purposes, Organization spaces and boards are protected by default to non-members.

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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.spreo.io/management/security-and-access-control.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.