SSO & Team Authentication
Configure Single Sign-On for enterprise team management.
Enterprise Feature
SSO is available for Business plan teams with 10+ members. Contact enterprise@pegboard.app to enable.
Supported Providers
PegBoard supports SAML 2.0 and OAuth 2.0 protocols for enterprise identity providers.
SAML 2.0
- • Okta
- • Azure AD / Entra ID
- • Google Workspace
- • OneLogin
- • Auth0
OAuth 2.0
- • Microsoft 365
- • Google Workspace
- • GitHub Enterprise
Configuration Steps
1. Request SSO Access
- 1
Contact enterprise@pegboard.app with your organization details
- 2
Provide your preferred identity provider (Okta, Azure AD, etc.)
- 3
Receive SSO configuration credentials and callback URLs
2. Configure Identity Provider
For Azure AD / Entra ID
- 1
Sign in to Azure Portal → Azure Active Directory → Enterprise Applications
- 2
Create New Application → Create your own application
- 3
Name:
PegBoard, Type: Non-gallery application - 4
Navigate to Single sign-on → Select SAML
Identifier (Entity ID):https://api.pegboard.app/saml/metadataReply URL (ACS):https://api.pegboard.app/saml/acs - 5
Download the Federation Metadata XML and send to PegBoard team
For Okta
- 1
Sign in to Okta Admin Dashboard → Applications → Create App Integration
- 2
Sign-in method: SAML 2.0 → Click Next
- 3
Configure SAML:
Single sign-on URL:https://api.pegboard.app/saml/acsAudience URI:https://api.pegboard.app/saml/metadata - 4
Copy the Metadata URL and send to PegBoard team
3. Enable for Your Team
- 1
Once configured, team members will see "Sign in with SSO" option
- 2
Users enter their corporate email to be redirected to your identity provider
- 3
After authentication, they're automatically added to your PegBoard team
User Provisioning
Automatic user provisioning and de-provisioning based on your identity provider.
SCIM Support
PegBoard supports SCIM 2.0 for automated user lifecycle management:
- • Automatic account creation when users join your organization
- • Role and permission sync from identity provider groups
- • Automatic deactivation when users leave your organization
- • Profile updates (name, email) sync automatically
Group Mapping
Map identity provider groups to PegBoard team roles:
PegBoard-Admins → Team AdminPegBoard-Users → MemberSecurity Best Practices
- • Enforce multi-factor authentication (MFA) at your identity provider level
- • Regularly review and audit user access logs
- • Use time-limited sessions and enforce re-authentication
- • Keep SAML certificates up to date before expiration