Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note
titleRole-Assignment Best Practices

The application requires a Global or Contract designation when a User Role is created. The Role's name should utilize a prefix or suffix that clearly identifies it as a Global or Contract-level Role. The examples below use:  "(C)" or "(G)" prefix.

  • Global Roles can only be assigned at the Global Level.
  • While the application allows Contract-level Roles to be assigned Globally, this is not recommended. Doing so can result in unintended data visibility and access to tools beyond a user's responsibility or authority.
    • Assigning a Contract-level Role to a user, gives the user access to that Contract and associated data.
    • Users should only be granted access to the Contracts for which they have work responsibilities or need to know.
    • Users should be assigned the lowest-level User Role that meets their needs. That is, if "Technician" meets their needs, they should not be assigned "Supervisor" role.


Refer to the Global and Contract the User Roles page for guidance on User Role creation and management. The  The following sample User Role permission sets may be helpful as you establish your new InfraLink instance:.

Table of Contents

Global User Role Examples

...