Sinch Agentic Tools
Sinch SDKs
Sinch CLI & Functions
Sinch ID is the identity you use to sign in to Sinch, including the Sinch Build Dashboard. This page covers signing in, protecting your sign-in with multi-factor authentication, and connecting your organization's identity provider through Single Sign-On.
Sinch ID is about signing in as a person. It's separate from API authentication. Applications authenticate with access keys and OAuth2 tokens, not your Sinch ID.
Sign in at dashboard.sinch.com with the email and password you set when you created your account or accepted a team invite.
If your organization has enabled Single Sign-On, you'll be redirected to your company's identity provider instead of entering a Sinch password.
- On the sign-in page, select Forgot password?
- Enter your email address.
- Follow the link in the email to set a new password.
If you sign in through SSO, password resets are handled by your identity provider, not by Sinch.
MFA (also called 2FA) adds a second step at sign-in, so a stolen password alone isn't enough to access your account. 2FA is mandatory. Every Sinch Build Dashboard user has been required to use it since 14 September 2022. Manage your user profile and 2FA at my.sinch.com (also reachable from the dashboard via the profile icon in the top-right → Manage my Sinch ID). Sinch ID supports three methods:
- SMS: a one-time code sent to your phone number.
- Authenticator app: a time-based code from Google Authenticator, Authy, or similar.
- Security key: a hardware security key.
- You can enroll more than one method. For example, use an authenticator app as your primary with SMS as backup. Save your recovery code somewhere safe; you'll need it if you lose access to your second factor.
- When SSO is enabled, your team signs in through your identity provider with your company credentials instead of a Sinch password.
Single Sign-On lets your team sign in to Sinch with your company's existing identity provider (IdP) over SAML 2.0. Access is governed by your IdP, so removing a user there removes their Sinch access too.
- One set of credentials for your team; nothing extra to remember.
- Central control: disable a user in your IdP and they lose Sinch access.
- Enforce your own password and MFA policies through the IdP.
SSO works in one of two ways:
Home Realm Discovery
- A team member goes to the Sinch sign-in page and enters their work email
- Sinch recognizes the email's domain and redirects them to your IdP
- The IdP authenticates them and asserts their identity back to Sinch (SAML)
- They land in the dashboard with the role assigned to them
Identity Platform Initiated
- A team member clicks a link from your company’s IdP
- The user is seamlessly logged in and redirect to a chosen default application
SSO is a request-only feature: you ask Sinch to enable it for your account rather than switching it on yourself. The high-level flow is:
- Request SSO for your account through Sinch support or your account team. See How do I get access to SAML?
- In your identity provider (Microsoft Entra ID, Okta, or another SAML 2.0 IdP), create a SAML application for Sinch and assign the users or groups who should have access.
- Download your IdP's XML metadata and provide it to Sinch to complete the connection. See How to provide your SAML configuration and enable SSO.
- Test sign-in with a pilot user before rolling the change out to your whole team.
Sinch ID SSO uses SAML 2.0 and is verified with Microsoft Entra ID and Okta. Other SAML 2.0 identity providers generally connect the same way.
- Team & access management: invite users and assign roles.
- Authentication methods: how applications authenticate to the API.
