Signing In
Insights accounts are not created in Insights. Your SIP installation creates them, from the name, email address, SIP user ID and authorized device groups it already holds for each user.
Reaching Insights
From SIP. Open the module menu on the toolbar and choose Insights. The entry appears once your instance is registered, and only for users whose SIP permissions allow it. Insights opens in a new browser tab, so a pop-up blocker can stop it.
Directly. https://insights.firemon.cloud, once you have an Insights password.
Start with the module menu. Going straight to the URL before you have ever arrived from SIP won't get you in, because until then there is no account to sign in to.
The first time
The first time you choose Insights from the module menu, SIP hands your details across, Insights creates your user, and you land on a page that asks you to set a password. It has to be at least 10 characters, and contain a lowercase letter, an uppercase letter and a number. After that, the same menu item takes you to the sign-in page with your username already filled in.
Your username is your email address. Usernames have to be unique across every FireMon Insights customer, so if yours is already taken, Insights builds one from your name instead, in the form first_last_123. Check the username on the sign-in page rather than assuming it.
If your organization signs in through an external identity provider, arriving from SIP sends you there instead, and there is no separate Insights password to set.
Where accounts come from
Users are created, enabled and disabled in SIP, under Administration > Access, and synced to Insights from there. Insights has no screen for adding a user, disabling one, or granting access to a device group. Your SIP installation holds the master record, and having the same controls in both places would give you two answers to the same question.
The device groups you can select in Insights are the ones your SIP permissions authorize. Users and Access covers the whole model, including what a user sees when they have no authorized groups.
When someone cannot sign in
Two causes, in the order worth checking.
They have never come in from SIP. The account is created on that first navigation from the module menu, not by the periodic user sync. Someone who goes straight to the Insights URL has nothing to sign in to. Send them through the module menu once.
There is no email address on their SIP account. Insights builds the account from the address SIP sends. Add one in Administration > Access, then have them use the module menu again.
Troubleshooting covers the rest, including the user who signs in successfully and then finds every page empty.