# Access and privacy

> Choose how people sign in on your custom domain, require single sign-on, and see which homepage and sign-up controls apply.

These settings decide who can sign in on your custom domain, and what anonymous visitors can do there. Each domain has its own settings, and only the organization’s **owner** can change them.

> **Running your own instance?**
>
> [Environment variables](/en/reference/environment-variables) lists the deployment-wide sign-in settings. Use this page for the custom domain’s controls.

## Sign-in settings

Sign-in settings choose which sign-in methods appear on your domain’s sign-in page. They need **Identity Plus** or **Team Plus**.

Sign-in on a custom domain is off until the owner sets it up here. The only exception is a working [SSO](/en/organizations/sso) connection, which is offered on its own.

A domain can only narrow the methods the service offers. It cannot add a method the service does not offer. Passkeys are tied to the main sign-in site and are not available on custom domains.

1. Open the user menu, choose **Domains**, then **Manage** next to the domain.

2. Under **Features**, choose **Configure Sign-In**.

3. Under **How can users sign in?**, choose one:

   * **Any available method**: every method the service offers. **Password** is always offered in this mode. **Email authentication** and **Single Sign-On** each have an **Allow on this domain** switch.
   * **One specific method**: only the method you pick, such as **Password**, **Email authentication** or **Single Sign-On**.
   * **Sign-in disabled**: nobody can sign in on this domain. Visitors to the sign-in page see a notice with a link back to the homepage.

Each choice is saved as soon as you make it. **Reset to defaults** removes the domain’s sign-in settings, so nobody can sign in on the domain with a password or an email link. A working SSO connection is kept and stays available.

These settings apply on your custom domain only. People can still sign in on the main site with their usual method.

### Require single sign-on

On **Team Plus**, the owner can connect the domain to an identity provider and then choose **One specific method** and **Single Sign-On**. Set up and test the connection first: restricting the domain to SSO before it works blocks sign-in there. See [Single sign-on (SSO)](/en/organizations/sso).

## Sign-up settings

Sign-up is off on every custom domain, and there is no setting to allow it. People who sign in with a password or an email link create their account on the main site.

[Single sign-on](/en/organizations/sso) is the exception. On a domain with a working SSO connection, a person’s first sign-in through the identity provider creates their account. They should not sign up on the main site first: an existing account that has not connected the provider is refused on the domain.

## Privacy options

What anonymous visitors can do on your domain is set by the domain’s **Homepage** setting: a private landing page, a form for creating secrets, or an incoming-secrets form. It is included on every plan. See [Homepage and incoming secrets](/en/custom-domains/homepage-and-incoming).

A domain has no setting that requires a passphrase or sets a default expiry for its secrets. Those are chosen for each secret; see [Sharing secrets](/en/share).

## Related

* [Single sign-on (SSO)](/en/organizations/sso) — connect your identity provider to a domain.
* [Homepage and incoming secrets](/en/custom-domains/homepage-and-incoming) — what visitors can do on your domain’s homepage.
* [Roles and permissions](/en/organizations/roles-and-permissions) — who can change a domain’s settings.

## Questions or need support?

Email [support@onetimesecret.com](mailto:support@onetimesecret.com) or use the [feedback form](https://onetimesecret.com/feedback).