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

# Access Control and SSO

The login methods BlueGamma supports, the access controls we can configure for your organisation, and Enterprise SSO.

BlueGamma offers several secure login methods and allows organisations to control how their users access the platform. This page outlines the available login options and the access controls that can be applied at no additional cost.

***

### **1. Supported Login Methods**

BlueGamma supports three login methods by default:

* **Email & Password -** Secure traditional login.
* **Magic Link (Passwordless Login) -** Users receive a one-click login link via email.
* **Login with Microsoft -** Users can authenticate using their Microsoft work account.

All options are available by default unless your organisation requests a different configuration.

***

### **2. Organisation-Level Access Control**

If required, BlueGamma can configure how your users authenticate.

**What BlueGamma can enforce for your organisation:**

**1. Enforce Microsoft-only login**

We can disable email/password and magic link logins, so users must log in through Microsoft.

**2. Disable or Enable specific login methods**

We can turn off any of the default methods for your tenant:

* Disable email/password
* Disable magic links
* Disable Microsoft login
* Allow only one chosen method

**3. Manage users in your organisation**

Organisation admins invite, remove and manage members themselves in Organisation settings. See [Adding and Removing Seats](https://www.bluegamma.io/documentation/account-and-team-management/adding-and-removing-seats.md).

***

### **3. Enterprise SSO**

Enterprise SSO is included in the Enterprise plan, for organisations wanting deeper identity integration.

**Enterprise SSO includes:**

* True SSO using Microsoft Entra ID, Okta, Ping, OneLogin, etc.
* Users authenticate directly with your organisation's identity provider
* Centralised provisioning and deprovisioning
* Optional SCIM provisioning
* Enforced SSO for all users
* Automatic user lifecycle management
* Dedicated onboarding support

***

### **4. Need Help or Want to Configure Access?**

To adjust login settings or enforce a specific access policy:

📩 **<support@bluegamma.io>**


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.bluegamma.io/documentation/account-and-team-management/security-and-access/access-control-and-sso.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 `automate deployments from our CI pipeline` 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.
