Skip to main content
Authentication settings is where you connect an outside sign-in provider to Overflow so your team and donors can log in with the account they already use.

​
Prerequisites

Before you begin, make sure you have:
  • Developer write permission in your nonprofit dashboard. Without it, you can view existing configurations but the row-level Edit and Delete actions will appear as a dash.
  • An application already set up with your identity provider, with a Client ID and Client Secret ready to paste in.
  • If your provider needs a base issuer URL or a tenant identifier, have that on hand too.

​
Set up authentication

1

Open Authentication settings

In your nonprofit dashboard, go to Developers → Authentication. The page opens with the heading Authentication settings, a short description, and a table of any configurations already in place.
2

Start a new configuration

Select New configuration in the top right. A form opens titled Create a new authentication configuration, split into three sections: Basic configuration, Provider authentication, and Redirect URLs.
3

Fill in the basic details

In Basic configuration, enter:
  • Configuration name. A label just for your team, so you can recognize this connection later. Something like Production donor profile sign-in works well.
  • Provider type. The identity provider you want to connect.
  • App. The Overflow product this sign-in will apply to. The available apps depend on the provider you chose, and the app updates automatically when the provider only supports one option.
4

Add your provider credentials

In Provider authentication, enter the details Overflow needs to reach your provider. The fields shown depend on the provider type you chose:
  • An Issuer URL or Tenant ID, so Overflow knows where to send sign-in requests. URL fields accept http or https addresses only.
  • Client ID. The public application identifier your provider issued.
  • Client secret. The private credential Overflow uses to complete the sign-in handshake. You only enter this when creating a configuration.
5

Copy the redirect and logout URLs into your provider

In Redirect URLs, Overflow generates two values for you:
  • Redirect URL. Where your provider should send users back after a successful sign-in.
  • Logout URL. Where your provider should send users after they sign out.
Both values are read-only and have a copy button. Paste them into your provider’s application settings so sign-in works end to end. If you change the provider or app before saving, these values refresh automatically.
6

Save the configuration

Select Create. The form closes, your new configuration appears in the table, and a success message confirms it saved.

​
Review existing configurations

The table on the main page gives you a quick read of every connection you have set up:
  • Name. The internal label you gave the configuration.
  • Provider. The provider type, shown with its brand logo.
  • App type. The Overflow product the configuration is attached to.
  • Created. When the configuration was first added. Configurations sort by this column, newest first, by default.
  • Last used. The most recent update or usage timestamp recorded for the configuration.
You can sort by Name, Created, or Last used by selecting the column header. The table shows 10 configurations per page, with paging controls when you have more than that. If nothing has been set up yet, you will see the message No authentication settings found.

​
Edit a configuration

From the row’s action menu, select Edit authentication configuration. The edit form lets you update:
  • The configuration name.
  • The provider type and app, within the combinations your provider supports.
  • The issuer URL or tenant identifier for the provider.
  • The Client ID.
The client secret is only entered when a configuration is first created, so it is not shown in the edit form. If your secret changes with your provider, plan to rotate it as part of a separate credential update. Select Save to apply your changes. The form closes, the table refreshes, and a success message confirms the update.

​
Delete a configuration

From the row’s action menu, select Delete configuration and confirm in the dialog. The configuration is removed, the table refreshes, and a success message confirms it. Sign-in paths that were using that configuration will no longer use it, so make sure you have a replacement in place before removing an active connection. This action cannot be undone.

​
Rules to keep in mind

  • You can have one active configuration per provider and app combination. If a configuration already exists for that pair, edit it instead of creating a new one.
  • The New configuration button is visible to anyone who can view the page. Creating, editing, or deleting still requires developer write permission in the dashboard.
  • The Last used column currently reflects the most recent time a configuration was updated, rather than a separate sign-in event.

​
FAQ

Some provider types only work with a single Overflow product. When you choose one of those providers, the app field updates automatically to the only supported option.
Row-level actions require developer write permission. Ask a dashboard admin to grant that permission, and the actions will appear.
The edit form does not include a client secret field. If your provider issues a new secret, delete the current configuration and create a fresh one with the new value.
Not at the same time. Each provider and app combination supports one active configuration.

​
Next step

Once your configuration is saved and the redirect and logout URLs are pasted into your provider, do a test sign-in to confirm the connection works. For request headers and endpoint-level authentication details, see the Overflow Authentication Reference.
Last modified on October 6, 2026