JEKA Support

All help articles

Incidents Across a Community Group

incidentscommunity-admin

Incidents Across a Community Group

Organizations that run several communities in MyWatchtower can organize them into a community group. When your role has incident access in more than one community of the group, the Incidents tab becomes a combined view: one list covering every group community you can access, instead of one community at a time.

How the combined view works

There is no switch to flip — the combined view turns on automatically:

Access is enforced per community: the combined list only ever includes communities where your role holds incident read permissions, and the server applies the same check independently. Colleagues whose roles cover a single community keep seeing only that community.

Working in the combined view

Filing an incident in a group

When you create an incident and your role has incident write permissions in more than one community of the group, the Report New Incident form shows a Community selector at the top. It defaults to the community you're currently viewing — pick a different one to file the incident there instead. The property search then looks up addresses in the community you chose. See Log an Incident for the rest of the form.

What stays per-community

The combined view applies to the Incidents list. The Dashboard tab's counters and widgets, and the Report History tab, cover the community you're currently viewing — switch communities to see another member's numbers. Generated reports likewise cover one community at a time (see Generating Incident Reports).

Need help?

Use the Contact Support form in the app, or contact your community's management office.

Was this article helpful?

YesNo

Still stuck? Open a ticket — the subject and this article are filled in for you — or email support@jekasoftware.com.