After deploying a new content pack, a user cannot access associated playbooks. What is the most likely cause?

Question

Options

• AThe engine is in maintenance mode
• BUser role lacks sufficient playbook permissions
• CThe agent is not upgraded
• DThe dashboard is misconfigured

• A
  6% (2)
• B
  91% (29)
• C
  3% (1)

Explanation

When a new content pack is deployed, its playbooks inherit permission requirements that must be explicitly granted to user roles - if the role hasn't been updated to include playbook access, the content exists but remains inaccessible to that user. Option B is correct because role-based access control (RBAC) is the most common gap after deploying new content: the pack deploys successfully, but no role assignments are made for it.

Why the distractors are wrong:

• A (maintenance mode): Maintenance mode typically affects the entire engine, not a specific user's access to specific playbooks - other users would be impacted too.
• C (agent not upgraded): An outdated agent affects execution/collection capabilities, not whether a user can view or access playbooks.
• D (misconfigured dashboard): Dashboard configuration controls what widgets or data panels display, not playbook visibility or permissions.

Memory tip: Think "deploy = permissions gap." Any time new content is added to a system with RBAC, ask "who has been granted access?" before troubleshooting infrastructure issues like agents, engines, or dashboards.

No community discussion yet for this question.