Security Considerations and Limitations

SAI360's Emissions Management module relies heavily on pre-determined data structures, hence configuration is locked down on most areas in this process including security.

To assist with the Security setup for this module, here are some details:

Security for Emissions Module

Topic

Comments

Access to Unit of Measure is required

To be able to use the Emissions Module, the users' role needs access to the Unit of Measure. It is necessary to manually define this access.

Security Roles

The Emissions Module comes pre-configured with two security roles to cater for Business users and Advanced users.

  • Policy Role - Emissions - Basic
  • Policy Role - Emissions - Advanced

Users must inherit at least one of the two roles to be able to access Emissions Management module and create new Emission Data.

note_awesome

NOTE:
If required, Administrators can define Read/ conditions on the Component level.

For example, if a Basic User is allowed to only access data specific to their location, a ‘Conditional’ Read can be defined at the component level.

 

Attribute Level Security

Configuring attribute level security is not supported for existing fields. However if new fields are created, attribute level security can be configured on those fields.

See Also

Emissions Administration

Material Inventory: Emission Factors

Metrics (Emission Types)

Constants

Calculations

Entering Formulas

Emission Sources

Time Periods

Acceptable Input Deviation

Outstanding Emissions Data Entry Reminder

Incomplete Emissions Data Notification

Defining the Email Body for Reminder to complete outstanding Emissions

Maintaining Referential Data

Emissions Management: Outstanding Data Generation & Result Calculation

External Material Reference