Blumira Users
SkillAI & modelsBlumira organization users: listing and filtering users, user roles, and looking up the user IDs required for finding assignment and access audits.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Blumira Users skill
What this skill tells your AI
The instructions your AI receives, as published by wyre-ai/msp-claude-plugins in msp-claude-plugins/blumira/blumira/skills/users/SKILL.md and read by ahel’s review.
Overview
Blumira users are organization members who can access the portal, investigate findings, and manage the environment. This skill covers user listing and lookup, primarily for finding assignment workflows.
Anti-triggers
- The end user named in a finding — these are Blumira portal
members (your analysts), not the M365 or AD account that triggered a
detection. Look that account up in
cipp-usersorinforcer-identity-governance. - Creating, disabling, or offboarding anyone — Blumira's user
surface is list-only; account lifecycle is
cipp-users. - Users in a managed client account —
blumira_users_listis an/org/*call; useblumira_msp_users_listinblumira-msp.
Key Concepts
User Roles
Users have roles that determine their permissions within the Blumira organization. The API exposes user identity and metadata for assignment and audit purposes.
User IDs
User IDs (UUIDs) are required when assigning findings to specific analysts. Use blumira_users_list to look up IDs.
API Patterns
List Users
blumira_users_list
page_size=50
Response includes user ID, name, email, and role information.
Filter Users
blumira_users_list
email.contains=@company.com
Common Workflows
Find User for Assignment
blumira_users_listto get all users- Identify the appropriate analyst by name or role
- Use their
user_idwithblumira_findings_assign
User Access Audit
blumira_users_listwith full pagination- Review all users with access to the organization
- Cross-reference with HR/directory for offboarded users
- Report any discrepancies
Error Handling
Empty User List
Cause: Token may not have permission to list users Solution: Verify JWT token has appropriate scope for user management.
Best Practices
- Cache user lists during triage sessions to avoid repeated API calls
- Use email filtering to quickly find specific users
- For MSP environments, use
blumira_msp_users_listwith account context - Document user-to-role mappings for escalation workflows
Related Skills
- Findings — Assigning findings to users
- API Patterns — Filtering and pagination
- MSP — Per-account user management
Signals
- GitHub stars
- 45
- Forks
- 24
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
blumira-users- Source
- github.com/wyre-ai/msp-claude-plugins