Single sign-on and the sign-in policy
On Sign-in & SSO you decide how people sign in to your company's account: with your company's identity provider (single sign-on), whether an electronic ID is required, and how long a sign-in lasts.
Who can do this: the owner and admins of a company account. Single sign-on and provisioning are included in Plan 1–3 and Enterprise.
Single sign-on (SSO)
With single sign-on, your staff sign in to Parasend with their work account at your identity provider. Parasend supports SAML 2.0 and has step-by-step guides for:
- Okta
- Microsoft Entra ID
- Google Workspace
- Any other SAML provider (JumpCloud, OneLogin, PingFederate, Keycloak, AD FS …)
Before you start, verify your e-mail domain under Team → Domains (see Let colleagues find your team). The first time each person signs in through SSO, they confirm who they are once with their electronic ID; after that their work account is enough.
Once SSO is on, the card shows the provider, the metadata, the certificate's expiry and the last test. Use Test with your own account after any change at your provider.
Require single sign-on
When SSO is required, members get into your account only through your identity provider, so someone you turn off there can't get in here. The owner and up to two named admins can always sign in with an electronic ID, in case your provider fails. API keys keep working.
Before you click Require SSO, Parasend lists the members who have never signed in through your provider. Make sure your provider has them.
Provisioning (SCIM)
With provisioning, Okta or Microsoft Entra ID adds, suspends and removes people in Parasend as soon as that changes on your side. You can also give roles from groups: put people in groups named after the roles (for example "Parasend Admins") and they get that role at once.
- Click Create token (you confirm with your electronic ID) and copy it: it is shown once. You can have two tokens, so one can be replaced without a gap.
- Under Without a group, choose the role and deliveries for people who are in none of the groups.
- Recent SCIM activity shows the latest calls from your provider.
Google Workspace has no provisioning for custom apps; there, requiring SSO is your leaver protection.
Sign-in policy
Under Sign-in, choose how members sign in and how long a sign-in lasts:
- Any sign-in: an electronic ID or a passkey.
- Electronic ID only: Auðkenni or Smart-ID, or a passkey set up after signing in with one.
- Sign out after inactivity: 15, 30, 45 or 60 minutes.
- Longest sign-in: 1, 2, 4, 8 or 12 hours.
Click Save. The change applies at once, on each member's next action.