Undestanding and assigning EDIS user permissions and Scope

Each EDIS user requires permission to access an Estate and Building, permissions can be requested by the user and must be approved by the Building Administrator.

Permissions ensure that thee right person has access to the right data, 

The screenshot below highlights the permission in the building:

  1. The estate is selected
  2. Click on the Green box to request additional permissions
  3. Lists the current permissions

Some examples

Example 1:

  • If a user does not have access to an estate they will not be able to see any buildings in the estate.
  • If a user does have access to an estate, but does not have access to a building, they will not be able to see data in the building.

Example 2:

  • If an electrician creates a certificate – only they will be able to sign it off, other users cannot sign off the certificate.  The electrician may opt to have a data administrator assist with capturing the data – this means the data administrator can edit the data, but only the electrician can sign it off.

Example 3:

  • The electrician will select the Qualifying Supervisor and after the electrician has verified the certificate it can then be approved/rejected by the supervisor. After the certificate has been approved – it is locked no longer editable/

Example 4:

A building administrator can approve estate and building access – based in the roles in the table below

Requesting access training videos

The table below explains each permission:

Permission namePermission Abbreviation

Permission scope

Estate Administrator


When a user creates an estate the user becomes the Estate Administrator.  There can only be one Estate Administrator.  The Estate Administrator is by default a Building Administrator,  and can approve Building Administrator permissions.  An estate requires at least one Estate Administrator.
Building AdministratorBAThe building administrators are approved by the Estate Administrator.  Building administrators can approve estate and building access when requested by a user.  This is an important role and should only be approved after careful consideration by the existing Building Administrators.
Estate VisibilityEV

When a user has requested Estate Visibility, they are able to view the buildings in the estate, but have no access to the buildings.  Access to each building must be requested, this can be done on a building by building basis or can be assigned to all buildings at the same time (bulk permissions).


The contractor permissions allow users to create certificates and request the sign-off by the Electrical Supervisor.

The contractor permission cannot edit distribution board schedules directly – all changes to a distribution board schedule must be done by creating a certificate and approving the certificate.  After the certificate has been completed the distribution board schedules will be automatically updated.

Electrical supervisorES

The electrical supervisor permission is primarily used to verify a certificate as a Qualifying Supervisor.

The electrical supervisor can approve or reject the certificate.

The electrical supervisor can also edit distribution board schedules directly.


The Designer role is primarily used to sign off a New Installation design.

The Design role is also useful when giving users Read only permissions.

If a client wants to view the EDIS data, they should request access to the estate and then be given DE permissions.

This will allow them to view (read only) data without changing it.

Data AdministratorDAThe data administrator role is provided where the electrician needs assistance in capturing data, this role can edit certificate data, but cannot sign off the certificate. It is a useful role but needs to be approved with due care.

TABLE: EDIS roles and permissions