Designing an Intelex security model for multiple sites

The three security groups Intelex suggests per application, aligned to licence types: a reporter who creates records at their own location and below, a coordinator who edits and moves records through workflow, and a configurator whom platform security cannot restrict.

Security groups accumulate one exception at a time: a plant manager who needs a neighboring site, a contractor coordinator who needs half an application, a maternity cover who needed access for six weeks two years ago and still has it. Nobody plans an environment with sixty groups in it. An Intelex security model that survives multiple sites gets built around the distinctions the platform can actually enforce, and that list is far shorter than an org chart.

How many roles is right?

Intelex's own guidance is roughly three groups per application, aligned to license types:

Group	Typical license	What it does
Reporter	Limited or Supervisor Access	Creates records at their own and sub-locations
Coordinator or owner	Full Access	Edits, moves records through workflow, runs reports
Configurator	System Administrator	Changes objects, fields, workflows and security

Three is a target, not a rule. The test is whether a fourth group makes a distinction the platform can enforce. If the difference is "seniority" or "which plant they sit at", it is not a group.

Free

Read every article, in full.

Every article on the site, start to finish
Sources cited and linked on all of them
New pieces on Intelex configuration and EHS practice

Would rather not sign up? Email me and I will send it over.