Most common reason: sequential dependencies
This article explains why some Navigator modules show as locked or disabled, what you need to complete first, and when a locked state might indicate a real problem.
Navigator modules are often designed to be completed in a sequence. A later module can be locked until earlier setup or prerequisite steps are completed.
What to do when a module is locked
Check earlier modules: confirm required setup steps are complete.
Look for tooltips or status text: these often indicate what is missing.
Wait for provisioning steps: some modules unlock only after background setup completes.
When it might be stuck
A module has been in a "being set up" state for an unusually long time.
The UI indicates setup should have completed, but unlock never occurs.
What to send Support
Which module is locked
Screenshot of the locked state and any tooltip text
How long it has been in that state
Your company name and environment (commercial vs GCC High)