Article Summary
Enable Single Sign-On (SSO) with Microsoft Azure AD or Google Workspace to allow users to authenticate using their existing work credentials. Once enabled, SSO becomes the required login method for all users in your organization.
Estimated Time
10 minutes
Prerequisites
Admin permissions
Administrator permissions in Microsoft Azure AD or Google Workspace (for authentication)
All users must have work email addresses matching their AutoRFP accounts
Coordination with team about upcoming login method change
โผ๏ธ CRITICAL: SSO is an organization-wide change that affects how all users sign in. All users will need to sign in using the chosen provider, and password-based login will be disabled after SSO is enforced.
Step-by-Step Instructions
Step 1: Access Integrations
Navigate to Organizational Settings from the main menu.
Select Integrations.
Locate the SSO section.
Step 2: Choose Your SSO Provider
Select your organization's identity provider:
Microsoft Azure AD: For organizations using Microsoft 365
Google Workspace: For organizations using Google Workspace
Note: The user enabling Microsoft SSO must be an admin in both Microsoft Azure AD and AutoRFP to complete the connection.
Step 3: Authenticate Your Account
Click the Authenticate button for your chosen provider.
Sign in using your work account credentials.
Ensure the email address matches your current AutoRFP account - authentication will fail if emails don't match.
Grant necessary permissions when prompted.
Step 4: Enable SSO
After successful authentication, click Enforce SSO.
Review the confirmation message carefully.
Confirm that you want to enable SSO for your organization.
Step 5: Communicate Changes to Users
Notify all users about the SSO implementation.
Inform them they'll use work credentials to log in.
Explain what to expect during their next login.
Please note: AutoRFP will require users with existing passwords to enter their AutoRFP.ai password one more time to transfer them to SSO.
๐กTips & Best Practices
Verify all user email addresses match between AutoRFP.ai and identity provider
Verify you have necessary admin permissions in both systems before starting
โ๐ผ Common Mistakes to Avoid
Enabling SSO without notifying users - creates confusion and login failures
Disabling SSO without planning for password resets - locks users out of accounts
Forgetting that SSO is organization-wide - affects all users immediately
Need Help?
๐ฌ Live Chat: Available in-app
๐ง Email: [email protected] or contact your Success Manager directly for urgent support.
๐ Learning Centre: learn.autorfp.ai/en


