Table 1 summarizes the permissions needed for modifying observation monitoring definitions according to the context they are defined for. Note that these permission only define who can create observation monitoring definitions. They are not checked before a specific observation monitoring definition is executed. I.e. if the permission to create a observation monitoring definition in a specific context is revoked from a user, the definitions the user created so far will remain active.
Table 2 summarizes the permissions needed for reading the observation monitoring definitions in different contexts.
Context |
Needed effective permission |
Feature |
Observation monitoring (6) |
Domain + feature type + feature subtype |
<%DATADOMAINPERMISSION_OBSERVATIONMONITORING%> AND Observation monitoring (6) |
Domain + feature type |
<%DATADOMAINPERMISSION_OBSERVATIONMONITORING%> AND Observation monitoring (6) |
Table 1: Permissions needed to create and modify observation monitoring definitions with different contexts
Context |
Needed effective permission |
Feature |
Read (0) |
Domain + feature type + feature subtype |
Read (0) |
Domain + feature type |
Read (0) |
Table 2: Permissions needed to display observation monitoring definitions with different contexts