feat(activity): Adding documentation for new user/event filter option

[Aiiaiiio]

☑️ Resolves

Documentation for Activity's new config option.

🖼️ Screenshots

✅ Checklist

• I have built the documentation locally and reviewed the output
• Screenshots are included for visual changes
• I have not moved or renamed pages (or added a redirect if I did)
• I have run codespell or similar and addressed any spelling issues

[Copilot]

Pull request overview

Note

Copilot couldn't run its full agentic review because no GitHub Actions runner was available. Make sure your repository has a runner available to run Copilot's review, or add a copilot-setup-steps.yml file specifying one with the runs-on attribute. See the docs for more details.

Adds admin manual documentation for a new Activity app configuration option that excludes specific event types from being logged for selected users.

Changes:

• Documented the new activity_log_exclude_users config option in the Activity configuration options table
• Added a dedicated section explaining the option with a config.php example

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

📖 Documentation Preview

🔍 Open preview →

📄 1 changed documentation page

• admin_manual/configuration_server/activity_configuration.rst

Last updated: Tue, 21 Jul 2026 08:13:18 GMT

[miaulalala]

Thanks for adding this! I cross-checked against nextcloud/activity's lib/Data.php (isExcludedAuthor()) and the config key/shape ('user' => ['event_type', ...]) matches exactly.

One wording nit though: the phrasing "For certain users, it might make sense to exclude some event types from being logged... For these users and event types a log record won't be created" reads as if this filters what shows up in that user's own activity feed.

Looking at the implementation, the filter is actually keyed on the event author ($event->getAuthor()), and it suppresses the activity record entirely — for every affected user's stream, not just the configured user's own. So 'alice' => ['file_created'] means "when alice creates a file, no activity entry is logged for anyone" (e.g. it also disappears from a shared folder's activity for other members) — not "alice stops seeing file_created events in her own feed."

Could we tweak the wording to make that clearer, something like:

For certain users, it might make sense to suppress activity log entries for actions they perform, for specific event types — for example to reduce noise from automated/service accounts. Set the config value activity_log_exclude_users in your config.php::

'activity_log_exclude_users' => [
'alice' => ['file_created'],
'bob' => ['file_created', 'file_changed'],
]

When one of these users performs one of the listed event types, no activity log record is created at all — including in other users' streams (e.g. shared folder activity).

Just want to make sure admins don't configure this expecting per-viewer filtering when it's actually a global suppression based on who performed the action.