Document alert tickets
README, INTEGRATIONS (the osTicket ticket API: fields, making the key, what is sent, what it can't do, what wasn't verified), NOTIFICATIONS (the rules, in one table), ROLES, DATABASE (the new table, the settings key, the internal flags, what deleting an integration does), and the Privacy page (the one new thing that leaves the app: an alert's text, to your osTicket). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
96c93ef924
commit
aec553f122
5 files changed
+86
-8
No files matched your search
@@ -82,6 +82,10 @@ even further, to admin only:
|
||||
- **Generator**: everyone can use it; the name lists it picks server names from
|
||||
are edited under Settings → Names, which is admin-only (and so is importing
|
||||
names from Skatteverket).
|
||||
- **Alert tickets**: everyone sees which alerts have an osTicket ticket (a
|
||||
badge on the Alerts page, linking to the ticket in osTicket); switching the
|
||||
feature on, choosing what opens a ticket, and sending a test ticket are
|
||||
under Settings → Alert tickets, which is admin-only.
|
||||
- Everything under **Settings** (notification channels, badge colors,
|
||||
display prefs, log retention, backup/restore) is admin-only, matching
|
||||
the page itself being admin-only.
|
||||
|
||||
Reference in new issue
Block a user