> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/security/enterprise-security.md).

# Enterprise Security

Explore enterprise security features in PowerShell Universal, including multiple authentication schemes and fine-grained Admin Console permissions.

PowerShell Universal provides enterprise security features to allow for integrating with existing authentication and authorization methods. It also includes fine grained Permissions that can restrict access the Admin Console for specific features.

Enterprise Security requires a [Server or Enterprise license](https://store.devolutions.net/package#psu).

## Multiple Challege Schemes

When multiple challenge schemes are configured (e.g. SAML2 and Windows), then PowerShell Universal will select the first scheme that is defined in `authentication.ps1` . When access a protected resource, like an app or the admin console, the highest priority scheme will be used.

The below example will use Windows authentication when access protected resources by default. If you wish to login with OpenID Connect, you would need to visit the login page and click the Login with OpenID Connect button.

```powershell
Set-PSUAuthenticationMethod -Type 'Windows'
Set-PSUAuthenticationMethod -Type 'OpenIDConnect'
```


---

# 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://docs.devolutions.net/powershell-universal/security/enterprise-security.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.