exclude protected users from user count in home api

[nikhilsinhaparseable]

Summary by CodeRabbit

• Bug Fixes
  • User count calculation now excludes protected accounts, changing how the system determines if users have been added beyond the default configuration.

[coderabbitai]

Walkthrough

The PR modifies the user count calculation in generate_home_response to exclude protected users from the total count, changing the filter logic to count only unprotected users in the membership map.

Changes

Cohort / File(s)	Summary
User Count Filter Logic src/prism/home/mod.rs	Modified user_count calculation to filter and count only unprotected users instead of all users in the membership map, affecting the user_added determination logic.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• parseablehq/parseable#1371: Modifies the same generate_home_response function in src/prism/home/mod.rs to restructure alerts and stats while this PR changes the user count filtering logic.

Suggested labels

for next release

Poem

🐰 Protected users now fade from sight,
As counts are filtered pure and bright,
A little hop, a logic change,
The home response, ever strange!

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request has no description provided by the author, missing all required sections including issue reference, description, solutions/rationale, key changes, and testing/documentation checkboxes.	Add a complete description following the template: reference issue #1576, explain the goal and rationale, describe key changes, and check off testing and documentation items.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: excluding protected users from the user count in the home API endpoint.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/prism/home/mod.rs`:
- Around line 162-166: The current logic computes user_count as number of
non-protected users but still uses user_added = user_count > 1, which
incorrectly requires two non-protected users; change the threshold to user_added
= user_count > 0 so a single non-protected user marks user_added. Update the
assignment of user_added in src/prism/home/mod.rs (references: users(),
tenant_id, DEFAULT_TENANT, user_count, user_added) and adjust the inline comment
to reflect "at least one non-protected user".

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 6b802298-b868-427a-ab13-07a14e7eaf24

📥 Commits

Reviewing files that changed from the base of the PR and between dd47c39 and f1fc7e7.

📒 Files selected for processing (1)

• src/prism/home/mod.rs