17 | | ||Subscriber ||Receiving alerts through defined communication modes ||Edit own contact details (email, phone, name, ...) || |
18 | | ||Alert Editor || || || |
19 | | ||Authorize || || || |
20 | | ||Implementer || || || |
21 | | ||Administrator || || || |
| 17 | ||Authenticated / Subscriber ||Receiving alerts through defined communication modes ||Edit own contact details (email, phone, name, ...) -> pr_contact, pr_person || |
| 18 | ||Alert Editor ||Can create the CAP Message and submit that for approval ||cap_alert (Create, Read, Update), cap_template (Read), cap_area (Read), pr_group [person' group](CRUD), Admin Based Subscription pr_subscription (CRUD) || |
| 19 | ||Alert Approver ||Besides Authorizing Message to disseminate, they can also act as CAP Editor || cap_alert (Create, Read, Update, Review, Approve), cap_template (Read), cap_area (Read), pr_group [person' group](CRUD), Admin Based Subscription pr_subscription (CRUD)|| |
| 20 | ||Implementer/ Administrator || Normally one time implementation||superuser, has access to all the functions || |