InnerWeb
Skip to main content

Report recipients: roles and location scope

In a plant with several halls not everyone needs every report. Report rules in InnerWeb are set per instance and per location scope, and recipients are specified by email addresses and roles. Below are recommendations on how to split rules so that each person gets data from their own area and nothing beyond it.

4
independent toggles for report content scope
Source: reporting module documentation
5
roles allowed to configure rules
Source: reporting module documentation

Who this recommendation is for

These recommendations apply to plants where several halls or departments operate and several recipients have different tasks: hall supervisors, the safety department, the technical department, the deliveries administrator, the director. When everyone receives everything, reports stop being read. When everyone receives only their own part, the chance that someone reacts goes up.

Order matters too. A report contains a ranking of external contractors, totals per department and a breakdown of hazardous work, so not every recipient needs to see data for the whole plant.

Recommendation 1: split rules by location scope

Report rules are set per instance and per location scope. An empty scope means all locations, so a rule without a restriction covers the whole plant. Two rules with different locations and recipients can run side by side, for example one for hall A with the hall A supervisor and another for hall B with a different supervisor.

Start with a restriction rather than an empty scope. An empty scope is convenient for a consolidated report for the director, but for hall supervisors it means they see data they cannot influence. A restriction reduces noise and makes responsibility easier to assign.

Sample number of rules in a plant with three halls

Sample number of rules in a plant with three hallsBar chart: three local rules, one for the safety department and one consolidated rule for the director.0123rulesLocal per hall: 3 rules3 rulesLocal per hallFor safety department: 1 rules1 rulesFor safety departmentConsolidated for director: 1 rules1 rulesConsolidated for director
Source: Sample calculation: three halls, one safety department rule and one consolidated rule

Recommendation 2: combine email addresses with roles

Recipients of a rule are specified by email addresses and by roles. An address suits a person outside the system, for example a board member who does not log in to the panel. A role suits positions that change hands, because a new person in the role starts receiving the report without the rule being changed.

A practical principle: roles for operational functions, addresses for individuals outside the system. This way staff rotation does not require reviewing every rule.

Recommendation 3: limit the group of people who configure rules

Administrator, supervisor, safety, technical and deliveries administrator roles can configure rules. This is a wide group, so it is worth setting an internal rule on who creates a new rule, who approves a change of recipients and who is responsible for the review.

Without such a rule, duplication easily happens. Two people create similar rules for the same hall and recipients receive two emails with the same data. A register of rules with an owner and the date of the last review solves this problem.

Recommendation 4: match the content scope to the recipient

The content scope of a report is switched on with four independent toggles: charts, details, analytics and comparison with the previous period. A hall supervisor usually needs details, the director needs charts and comparison, and the safety department needs analytics. Separate rules for different recipients let you tailor the content instead of sending everything to everyone.

Formats can also differ: PDF for a quick review, XLSX for people who want to filter the data. The PL or EN language is set per rule, which helps when the recipient is a manager from abroad.

Recommendation 5: a consolidated report kept separate from local reports

In a plant with several halls two levels are useful: local rules per hall for supervisors, and one rule with an empty scope for the director. The consolidated report allows halls to be compared, while local reports point to specific actions.

InnerWeb works as an independent system that complements the client's existing systems, such as access control, time and attendance, HR and ERP. Reports cover data collected in InnerWeb, so the recipient knows that the figures come from a single source.

Video

Frequently asked questions

What does an empty location scope in a rule mean?

It means all locations. The rule then covers the whole plant, which suits a consolidated report for the director.

Does a recipient need an account in the system?

No. Recipients are specified by email addresses and roles, so an address can belong to a person outside the system.

Who can create rules?

Administrator, supervisor, safety, technical and deliveries administrator roles. It is worth agreeing internally who approves changes.

Let us split reports between roles in your plant

We will show rule configuration per hall and per role, together with a report preview. Book a short demo of the reporting module.

Let's talk