Root admins to differenciate "Trusted hosts"

[Betree]

User story

As a platform admin, I need:

• To make sure that some sensitive features are only enabled for the hosts we trust (e.g. Create a 'feed' for all Updates posted on OC #4564, Manually subscribe to Updates #1445)
• To get accurate stats about the activity on the platform (i.e. spammers and testers should not get mixed up with legit hosts)

MVP

On the root admin dashboard, add a "Manage hosts" section. This section should list all hosts, and for each of them admins should be able to:

• Mark them as "trusted" (=> they will be included in fiscal reports, will have special features enabled, etc)
• Optionally: Enable/disable features for them using checkboxes (Root admin action to enable/disable features for an account #4627)

---

Triage Template (team only)

This template is for members of the team to triage for prioritization. For more guidance see https://www.loom.com/share/369ab467fbc64dec848085d38ff57ca0:

P1 high frequency, high impact
P2 low frequency, high impact
P3 high frequency, low impact
P4 low frequency, low impact

Examples of high impact - a problem affects users during an essential process (expenses and payments > onboarding and registration > contributing) with no workaround.

High frequency - >10% of users affected (measured as a proportion of total potential users for this case).

[alanna]

I think this would be really helpful for lots of reasons, and reduce friction for experimenting with new functionality, while increasing accuracy of certain metrics.

[Betree]

@SudharakaP started a PR to introduce this field in the API: opencollective/opencollective-api#6735. So this issue is now only about introducing a way for root admins to manage this flag.