Overview
SensGrid uses corporate credentials via Microsoft Azure AD / B2C for secure authentication. You do not need to manage a separate SensGrid password; instead, you log in using your organizational account.
Prerequisites
Before attempting to log in, ensure you have:
A valid corporate email account (e.g., CPB Contractors or an approved partner domain).
Been granted access permissions to the SensGrid platform by your system administrator.
Multi-Factor Authentication (MFA) set up on your corporate account if required by your organization.
Logging In
Follow these steps to access the platform:
Navigate to the Platform:
Open your web browser and navigate to the SensGrid application URL (e.g., https://dev.sensgrid.com.au for development/test, or the production URL provided by your administrator).
Automatic Redirection:
Enter Credentials:
On the Microsoft sign-in page, enter your full corporate email address and click Next.
Enter your corporate password.
If prompted, approve the Multi-Factor Authentication (MFA) request on your authenticator app or enter the verification code sent to your device.
Access the Landing Page:
Note: Upon your first login, the platform registers your profile and configures your account settings. This may take a few additional seconds.
Troubleshooting
If you encounter issues during the login process, try the following solutions:
Redirection Loops
If the browser continuously redirects between SensGrid and the Microsoft login page:
Clear your browser cache and cookies, or try opening an InPrivate / Incognito window.
Ensure that your browser allows cookies and local storage for the SensGrid domain.
Access Denied / Permission Errors
If you see an authorization error screen after entering your credentials:
Your corporate account has authenticated successfully, but your email has not yet been authorized in the SensGrid user directory. Contact your project administrator to request access.
Session Expiry
For security, your authentication session will expire periodically. If your session expires:
The platform will attempt to silently refresh your token.
If silent refresh fails (for example, after a long period of inactivity), you will be prompted to log in again.


