A team member with access to their own admin partition cannot use aaad.debug from the CLI. What is the most likely cause?

• A. The team member is NOT using the CLI correctly.
• B. The team member needs to troubleshoot the issue from the GUI.
• C. The team member does NOT have Shell access by design.
• D. The team member does NOT have permission to use the CLI.

Answer: (C)

Shell access is controlled separately from admin partition access, and some debugging tools are available only when you have direct shell access. aaad.debug is a debugging utility that runs in the system’s shell, not through the standard admin CLI. If a team member has access to their own admin partition but no shell session, they won’t be able to execute such a command by design. This isn’t about using the CLI incorrectly, needing to troubleshoot from the GUI, or lacking general CLI permissions; it’s about the deliberate restriction that prevents shell-level commands from being run by users who don’t have shell access. If this capability is needed, shell access must be granted (or the command must be run by someone with shell privileges).