FAQ - Why is the Employee Type field important when creating a System User record?

Mohammed Jamal Updated by Mohammed Jamal

The Employee Type given impacts which other Employee Types the user can see, as follows:

  • No = User cannot see this type of User (except their own record if type being compared is their own)
  • Yes = User can see and edit this type of user record (as long as user is also in the same Team)

Can view other Core System User records?

Can view other Provider System User records?

Can view other Rostered System User records?

Can view other System Administrator records?

Can view other Local System Administrator record?

Core System User

No

No

Yes

No

No

Provider System User

No

No

Yes

No

No

Rostered System User

No

No

Yes

No

No

Local System Administrator

Yes

Yes

Yes

Yes

Yes

System Administrator

Yes

Yes

Yes

Yes

Yes

For example:

  • A Core System User cannot see other Core System users records but can see their own user record
  • A Core System User cannot see any Provider System User records
  • A Rostered System User, such as a Care Worker, can select another Care Worker when entering data into the system about who assisted them with a Care Task. However, this Care Worker would not be able to choose a Core or Provider System User as assisting them
  • A Provider System User can select a Rostered System User to attend a Care Shift, but cannot select a Provider System User to attend a Care Shift

It also impacts which other User Employee Types can be created by the User:

Employee Type

Who Can Create

System Admin

System Admin

Local System Admin

System Admin

Local System Admin

Provider User

System Admin

Local System Admin

Core User

System Admin

Local System Admin

Provider User

Rostered User

System Admin

Local System Admin

Provider User

Core User

Was this article useful?

FAQ - Why am I seeing an error message in the Mobile App about option-set data not available?

Contact