SAML Single Sign-On for Your Business Card Portal: Okta, Entra ID, JumpCloud and Ping
What single sign-on means for your business card portal, in plain English, and how to set up SAML SSO in Brandly with Okta, Microsoft Entra ID, JumpCloud, Ping or any SAML provider.
On this page
Single sign-on (SSO) means your employees sign in once, with their company account, and that one sign-in opens Brandly along with their other work apps. No extra password. SAML is how it works behind the scenes: your company’s identity provider, such as Okta, Microsoft Entra ID, JumpCloud or Ping, checks who the person is and tells Brandly, “they’re with us,” along with their name and title, which fill in their business card. SAML SSO is included in Business Plus, $99 a year.
For a lot of companies, a business card portal isn’t approved until it passes the IT checklist, and the first item on that list is usually single sign-on. Employees shouldn’t need another password, and IT wants access managed in one place, along with every other tool. This guide explains SSO in plain English, what changes for your team, and how to set it up.
What is single sign-on?
Think of your company’s sign-in as a key. Without SSO, every app has its own lock, and employees carry a different key, or password, for each one. With SSO, one company key opens every door: email, HR, and your business card portal.
- Employees sign in once and get into all their work apps, with no extra passwords to remember or reset.
- IT decides who gets in, and turns access off, in one place: the identity provider.
- Security policies, such as multi-factor authentication (MFA), apply to every connected app automatically.
How SAML works: the front desk
SAML is the standard behind most company single sign-on. It works like a front desk in an office building: your company checks who you are, then tells Brandly, “They’re with us.”
1. You sign in once
At your company's sign-in page, such as Okta or Microsoft, with your usual password and MFA.
2. Your company vouches for you
Your identity provider sends Brandly a signed note: "they're with us," plus your name and title. No password is shared.
3. Brandly lets you in
You're signed in to your company portal, and your card is already filled in from your company profile.
Brandly never sees the employee’s password. It trusts the signed message from your identity provider, the same way a building trusts the badge its own front desk issued.
What changes for your team
For employees
Employees sign in with their work account, with no Brandly password. They can get in two ways:
- From www.brandly.com. They type their work email. Brandly recognizes your company’s email domain and sends them to your identity provider.
- From your portal’s join link. This is the link you share with your team. Anyone your identity provider lets through can sign in, whatever their email domain.
If your identity provider asks for MFA or a managed device, that still applies.
For IT
| What | How it works |
|---|---|
| Accounts | Created the first time someone signs in through SSO (just-in-time provisioning). No need to create users ahead of time. |
| Existing users | Matched by email. They keep their account and order history. |
| Access | Only people your identity provider lets through can sign in. Assign the app to the groups who order cards. |
| Card details | Name, title and phone numbers can come from your directory and update at every sign-in. When HR changes a title, the next card shows it. |
| Offboarding | No SCIM yet. Removing someone from your identity provider stops SSO sign-in. Also remove them from your Brandly team. |
Which attributes to map
Your identity provider needs two things: the NameID and the attributes.
NameID. Set it to the user’s email address. Brandly matches accounts by email, so this is required.
Attributes. These are optional, but they’re what makes SSO useful for business cards. Use plain attribute names, without a namespace or URI prefix.
| Attribute | What it does |
|---|---|
name |
Display name. Brandly splits it into first and last name automatically. |
first_name and last_name |
Use these instead of name if you want to control the split. |
Your template fields, such as title and phone numbers |
Fill the matching fields on the employee’s profile and card. |
Pass either name or first_name plus last_name. The exact names for your template fields are listed on the SSO Settings page in your portal.
Tips from teams that have done this:
- Start with name and title. Those matter most on a card and are usually accurate in the directory.
- Only map fields your directory keeps current. Each sign-in overwrites the profile, so an out-of-date phone number in the directory would replace a correct one.
- Use the preferred first name if your directory has one. People want the name they go by on their card.
- Multiple offices? We can map a location attribute to an office address saved in your portal. Ask us to turn it on.
How to set it up
Most teams finish in under an hour, and most of that time is spent in the identity provider.
| Step | Where | What to do |
|---|---|---|
| 1 | Brandly | Go to Settings → Sign-On Settings → SSO Settings. Download the Brandly metadata, or copy the Entity ID and ACS URL. Check your email domains are listed. |
| 2 | Identity provider | Create a SAML app, upload the Brandly metadata, set the NameID to email, add attributes and assign groups. Download the identity provider’s metadata. |
| 3 | Brandly | Upload the identity provider’s metadata on the SSO Settings page. Add Single Sign-On to the Join with link options. |
| 4 | Test | Log out, open your join link and sign in through SSO, or ask a colleague to try. Then share the link with your team. |
SSO is part of Business Plus. If you don’t see SSO Settings in your portal, email [email protected].
Notes for each identity provider
The steps above work for any SAML 2.0 provider. Here’s where the settings are in the four we’re asked about most.
Okta
- In the Okta Admin Console, go to Applications → Applications → Create App Integration, choose SAML 2.0 and name the app Brandly.
- Fill in the SAML settings:
| Okta field | Value |
|---|---|
| Single sign-on URL | Brandly’s ACS URL (check “Use this for Recipient URL and Destination URL”) |
| Audience URI (SP Entity ID) | Brandly’s Entity ID |
| Name ID format | EmailAddress |
| Application username |
- Under Attribute Statements, leave Name format as Unspecified and add the fields you want on cards, using the names exactly as Brandly lists them:
| Name | Value |
|---|---|
first_name |
user.firstName |
last_name |
user.lastName |
title |
user.title |
Phone numbers work the same way, with values like user.primaryPhone or user.mobilePhone. If your directory keeps a preferred name in user.nickName, use user.nickName != null ? user.nickName : user.firstName for first_name.
- When Okta asks, choose that you’re an Okta customer adding an internal app, and click Finish.
- On the Assignments tab, assign the groups who order business cards. New hires get access as soon as they’re added to the group.
- On the Sign On tab, open the Metadata URL, save the XML and upload it on Brandly’s SSO Settings page.
Microsoft Entra ID
In the Entra admin center, go to Enterprise applications → New application → Create your own application and choose the non-gallery option. Under Single sign-on, pick SAML. Enter the Entity ID as the Identifier and the ACS URL as the Reply URL, or upload the Brandly metadata.
Entra adds a long namespace to every claim by default. Brandly expects plain names, so edit each claim, clear the Namespace field and rename it to name, title and so on. Make sure the unique user identifier is an email attribute. Then download the Federation Metadata XML and assign users or groups.
JumpCloud
In the JumpCloud Admin Portal, go to SSO Applications → Add New Application and choose a custom SAML app. Enter Brandly’s Entity ID as the SP Entity ID and the ACS URL as the ACS URL. Give the app its own IdP Entity ID, set the SAMLSubject NameID to email, add your attributes and bind the user groups that need access. Export the metadata once you’ve saved the app.
Ping Identity
In PingOne, go to Applications, add a new application and choose SAML. Import the Brandly metadata or enter the ACS URL and Entity ID. Map the SAML_SUBJECT to email, add your attribute mappings and enable the app for the right groups. Then download the metadata from the app’s configuration tab.
Something not working?
The SSO Settings page keeps a log of recent sign-ins, with the attributes your identity provider sent each time. If a title isn’t showing up on cards, check the log first. Usually the attribute has a namespace, a different name or is missing. If the log doesn’t explain it, email [email protected] and we’ll go through it with you.
- Upgrade to Business Plus from Billing → Plan.
- Set the NameID to email.
- Map name and title first, and only fields your directory keeps current.
- Assign the groups who order business cards.
- Add SSO to the Join with link options, then test with the join link.
- Add Brandly to your offboarding checklist, since there’s no SCIM yet.
SSO FAQs
What is single sign-on (SSO)?
Single sign-on means employees sign in once, with their company account, and that one sign-in opens all the work apps the company connects to it. They don’t need a separate password for each app, and IT controls who can get in from one place.
What is SAML?
SAML is the standard that makes single sign-on work between your company and an app. Your identity provider, such as Okta or Microsoft Entra ID, checks who someone is, then sends the app a signed message that says, in effect, “this person is with us,” along with details like their name and title.
Which identity providers work with Brandly?
Any identity provider that supports SAML 2.0, including Okta, Microsoft Entra ID (formerly Azure AD), JumpCloud, Ping Identity, Google Workspace and OneLogin.
Do we have to create Brandly accounts for everyone first?
No. Brandly creates each person’s account the first time they sign in through SSO, and adds them to your team. People who already use Brandly are matched by email and keep their order history.
Does Brandly support SCIM?
Not yet. Removing someone from your identity provider stops them signing in through SSO, but you should also remove them from your Brandly team as part of offboarding.
How much does SSO cost?
SAML SSO is included in Brandly Business Plus, $99 a year per team. Setup help is free.
What it costs
SAML SSO is included in Business Plus, $99 a year per team, along with monthly invoicing and vCard+. There’s no extra charge for setup, and we’ll help you configure your identity provider if you need it.
If your team already uses Brandly, upgrade from Billing → Plan, then follow the steps above. Still comparing options? Read what a business card portal is, or contact our team and we’ll walk your IT team through it.
Set Up Your Free Business Card Portal
Get Started