# Sign-in rules

As an admin, you can enforce secure sign-in methods for all members by requiring authentication via **Google** or **SAML SSO** (requires pre-configuration).

To configure, visit [Settings > Organisation](https://app.spike.sh/settings/general/organisation).

![Sign-In Rules on Spike](/files/fQJTGzmDDgljJ6qQBxZd)

## Enforce Google or SAML SSO

When enabled:

* **Google Sign-In:** Users must connect their Google accounts to log in.
* **SAML SSO:** Users must authenticate through your identity provider. Access will be restricted otherwise.

Based on your settings, the invite sign-up page will automatically adjust to display only the allowed sign-in method.

## Restrict Email Domains

Admins can further control access by restricting sign-ins to specific email domains. Once configured, only users with the approved domain(s) can join and log in to Spike.


---

# Agent Instructions: 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:

```
GET https://docs.spike.sh/administration/sign-in-rules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.