Set up SAML single sign-on so your team logs in to Taskade with their Okta credentials. The setup takes about 10 minutes, in Okta first and then in Taskade.
TL;DR: In Okta, create a SAML 2.0 app with Single sign-on URL
https://www.taskade.com/saml/sso/login/callbackand Audience URIhttps://www.taskade.com/saml/sso/metadata. Map anuser.email. Copy Okta's SSO URL, Issuer, and X.509 certificate into Settings → Organization → SAML SSO in Taskade. SAML is on Business, Max, and Enterprise. Enterprise adds SCIM provisioning.
In this guide, you will:
- Create a Taskade app integration in Okta
- Connect Okta to your Taskade organization
- Assign Taskade to your people
What Is SAML?
SAML is the security standard that lets your team sign in to Taskade with the Okta credentials they already use. They need no second password. Joiners, movers, and leavers stay managed in Okta.
Before You Start
You need admin access in Okta and a Taskade plan that includes SAML.
| Requirement | Details |
|---|---|
| Plan | Business, Max, or Enterprise |
| Your Taskade account | Uses your company email address, not a personal one, and the email address is verified |
| Okta access | You can create app integrations in the Okta admin dashboard |
| Time | About 10 minutes |
Important: If your team already uses Taskade, your identity provider takes ownership of those accounts. Tell your team before you turn on SAML.
Step 1: Create the App Integration in Okta
Okta needs an app integration for Taskade.
- In your Okta dashboard, go to Applications.
- Click Create App Integration.
- Choose SAML 2.0, then click Next.
- In General Settings, type "Taskade" as the App name. You can also upload a logo.
Step 2: Enter the Taskade Details in Okta
The Configure SAML screen takes the Taskade values.
| Field | Value |
|---|---|
| Single sign-on URL | https://www.taskade.com/saml/sso/login/callback |
| Audience URI (SP Entity ID) | https://www.taskade.com/saml/sso/metadata |
| Name ID format | EmailAddress |
- Type each value from the table.
- Keep Use this for Recipient URL and Destination URL checked.
- Go to Attribute Statements (optional).
- Add an attribute with Name
emailand Valueuser.email.
Step 3: Finish the Okta Setup
Okta then shows the values that Taskade needs.
- Scroll down and click Next.
- When Okta asks, select I'm an Okta customer adding an internal app.
- If Okta asks "Which app pages did you consult to configure SAML?", paste
https://www.taskade.com/learn/account/saml-okta. Paste the same link for "Did you find SAML docs for this app?" - Scroll down and click Finish.
- On the next page, find SAML Setup on the right and click View SAML setup instructions.
- Keep this page open. You copy three values from it in Step 4.
Step 4: Paste the Okta Values Into Taskade
The SAML SSO form in Taskade takes the values from the Okta instructions page.
| Taskade field | What to paste from the Okta instructions page |
|---|---|
| Domain | Your company domain, for example company.com, without https:// or www. |
| SSO URL | Identity Provider Single Sign-On URL |
| IDP Issuer | Identity Provider Issuer |
| IDP Public Signing Cert | X.509 Certificate |
- Go to taskade.com/settings and open Organization, then SAML SSO.
- Type each value from the table.
- Under Default Workspace, select the workspace that people sign in to. It must be on the Business plan or above and owned by you.
- Click Configure.
┌──────────────────────────────────────────────────────────┐
│ SAML │
│ Configure single sign-on using SAML identity providers │
│ (Okta, Google Workspace, OneLogin, Auth0). │
│ Domain [ company.com ] │
│ SSO URL [ ] │
│ IDP Issuer [ ] │
│ IDP Public Signing Cert [ ] │
│ Default Workspace [x] Your workspace │
│ [ Configure ] │
└──────────────────────────────────────────────────────────┘
You cannot change the default workspace after you configure it. To change it later, contact support@taskade.com.
Step 5: Assign Taskade to Your People
People must have the app in Okta before they can log in.
- Open the Okta dashboard.
- Assign the Taskade app to the people or groups in your directory.
You Are Done When
A teammate goes to taskade.com/login, clicks Log in with Single Sign-On, signs in with Okta, and lands in your workspace. A new teammate can also start at taskade.com/signup. There, Sign up with Single Sign-On is a text link under the Google and Apple buttons.
Troubleshooting
Find what you see in the left column, then do the fix.
| What you see | Why | Fix |
|---|---|---|
| No workspace to pick under Default Workspace | You do not own a workspace on Business or above | Upgrade a workspace that you own, then open the form again. |
| Log in with Single Sign-On does not accept an email | The email domain does not match the Domain field | Type the domain exactly as company.com, with no https:// or www.. |
| Okta refuses the sign-in | The person is not assigned to the Taskade app | Assign the app to that person or group in Okta. |
Frequently Asked Questions
Which Taskade plans include SAML single sign-on?
Business, Max, and Enterprise. Enterprise also adds SCIM provisioning, which creates and removes accounts from Okta. See SCIM via Okta.
Does SAML change sign-in for my published apps?
No. SAML controls how your team logs in to Taskade. Sign-in for the visitors of your published Taskade Genesis apps works on every plan, and a custom domain for an app needs Business or above.
Can I change the default workspace later?
Not from the form. Contact support@taskade.com to change it.
Next Steps
Add automatic accounts and more protection on top of single sign-on.
- Provision accounts: Automate joiners and leavers with SCIM via Okta.
- Use another provider: See SAML via Google Workspace or SAML via Azure AD.
- Add a second step: Turn on Two-Factor Authentication.
- Hand off the workspace: See Transfer Workspace Ownership.
- Compare plans: See what each tier includes in the Plan Matrix.