We understand the importance of security and convenience, which is why we offer a range of methods for you to access our platform. Below, we break down all available login methods we provide.
1. E-mail and Password
This is the most conventional way to log in. A user will be asked to register their email and create their own password.
To log in with this E-Mail and Password:
Navigate to the Ignite login page.
Enter your registered email address and password.
Click 'Login'.
Ensure your password is strong, unique, and kept confidential for optimal security.
🔒 Security Pro's and Con's:
🟢 Easy set-up.
🟢 Can use any email.
🔴 Password strength up to each user.
🔴 Anyone invited to the workspace can access Ignite.
🔴 Users must be manually removed from Ignite.
2. Linking an E-mail to Microsoft with Social Sign On
Social Sign On is all about leveraging your existing accounts with popular platforms like Microsoft for quicker access. Ignite currently only supports Social Sign On with Microsoft.
How to link your E-mail to Microsoft
In order to use Microsoft Social Sign On, you will first need to link your account to Microsoft.
You can follow the guide in this article for more details: Linking an Account to Microsoft
To log in with this Microsoft Social Sign On:
Ensure you have linked your Microsoft account as per the step above.
Enter your E-mail and click on Log In.
You'll be redirected to Microsoft's login page - this step will auto-complete if you already are logged into Microsoft.
Once the information is verified, you will be redirected back to Ignite and logged in.
🔒 Security Pro's and Con's:
🟢 Verifies Accounts via Microsoft.
🟢 Convenient, just needs email to log in once account is verified.
🔴 Requires additional setup (And may need an Outlook admin to verify your account).
🔴 Users must still be manually removed from Ignite.
For Administrators: In your workspace settings, you can enforce Social Sign On for all users - requiring all users to log in via their Microsoft E-mail accounts. If Social Sign On is not enforced, linking the account will be optional.
3. Linking an Email Domain to Azure AD with Federation for Single Sign On
Single Sign On (SSO) means one set of credentials gives you access to multiple applications:
Note: The process below is just an example, and the final implementation by Ignite might be different.
On the Ignite login page, enter your email.
If you're already logged into an Azure AD federated service, you'll be instantly redirected and logged into Ignite. If not, you'll be prompted to login to your organization's Azure AD account.
Once authenticated with Azure AD, you'll be brought back to Ignite and logged in automatically.
🔒 Security Pro's and Con's:
🟢 Only users approved in Azure AD are able to access Ignite.
🟢 A user is automatically loses access to Ignite when removed from Azure AD.
🟢 Roles are automatically assigned from Azure AD.
🔴 User Management must be handled by Azure AD Admin team.
The Difference Between Social Sign On and Single Sign On (SSO)
Social Sign On (SSO): This is when a user utilizes their existing account on a social platform (like Microsoft, Facebook, or Google) to sign in to another unrelated platform (in this case, Ignite). The primary benefit is reduced password fatigue and faster onboarding since users won’t need to remember another username/password combination.
Single Sign On (also abbreviated as SSO): A bit confusing, right? While the abbreviation is the same, the concept is different. Here, a user logs in once to gain access to multiple systems without being prompted to log in again for each one. It's common in enterprise settings where a suite of tools or applications are used. This method can enhance user productivity and security by reducing the number of times a user has to log in and remember different credentials.
We hope this guide provides a clearer understanding of how to access Ignite and the login methods we support. Should you have further queries, don't hesitate to reach out to our support team!