Skip to content

Users FAQ

Why do the Attendance and Worklog hours not match?

Section titled “Why do the Attendance and Worklog hours not match?”

Because they count different things. Attendance is the shift — check in to check out, ten hours for somebody in at 10 and out at 8. Worklog is the work — start job to finish job, so two jobs of three and two hours make five. Both are right for the same day. See how users work.

Either — both tabs produce an amount, and the choice is yours. Attendance works the salary out from the shift, which is what a permanent employee on a monthly wage is paid for. Worklog multiplies the month’s job time by the person’s rate, which fits somebody paid for the hours they actually put in. See paying from the worklog instead.

A saved set of people, built from users who already exist. It saves picking the same names one at a time whenever that same handful is needed — Assign Fieldworker(s) on a job takes a group, and everybody in it drops into the field as individual names. See groups.

Can a user exist without being in a group?

Section titled “Can a user exist without being in a group?”

Yes. Users come first and groups are built from them, so a person’s record is complete whether or not they are in one. Nothing on the new-user form asks for a group.

Can somebody check in with no jobs assigned?

Section titled “Can somebody check in with no jobs assigned?”

Yes. Attendance and job assignment are separate — Check In starts the day whether or not there is work on it, and the day is recorded either way. See checking in does not need a job.

How do I edit a check-in or check-out time?

Section titled “How do I edit a check-in or check-out time?”

On the person’s Attendance tab, pick the day’s row in the Check In / Check Out report and edit the time. It changes the Captured Log Time; the attendance policies then work the Final Log Time out from your corrected figure. See correcting a day.

No. Attendance records cannot be deleted, only edited — a wrong day is corrected on the Attendance tab of that person’s record rather than removed. See correcting a day.

Somebody forgot to check out. What happens to that day?

Section titled “Somebody forgot to check out. What happens to that day?”

With Auto Check-Out switched on, the day is closed off at their shift end time when they next check in. Without it the day stays open. See auto check-out.

Can an Admin be converted into a Fieldworker?

Section titled “Can an Admin be converted into a Fieldworker?”

Yes, and without creating a second account. Open their record, Edit User, and change the Type. They keep the same login and the same history — jobs, attendance, worklog and payment record all stay with them. See the two types you create.

Can two people have the same mobile number or email address?

Section titled “Can two people have the same mobile number or email address?”

Yes to both. EyeOnTask checks neither for uniqueness, so two users can be saved on the same mobile number — a shared works phone, a crew on one line — and two users can be saved on the same email address, which suits a crew sharing an inbox.

What has to be theirs alone is the Username, because that is what they sign in with. Contact details identify how to reach somebody; the username identifies the account. See adding a user.

Check two things on their record: their Status is Active, and they are using their Username rather than their email address. Both admins and fieldworkers can sign in to the app, so the type is not what is stopping them. See the user page.

They are probably inactive. Tick Show Inactive Users above the list, or set Status to All in Table View.

Does deleting a user delete their expenses?

Section titled “Does deleting a user delete their expenses?”

No. Deleting removes the person from the account, not the account’s history of them — their expenses and the figures they fed stay for reporting. See deleting someone.

Because they have jobs created against them. The app will not delete anybody who does, so Inactive is the route for them — which is the right one anyway, since their history is worth keeping. See making someone inactive.

Can an inactive fieldworker still submit expenses?

Section titled “Can an inactive fieldworker still submit expenses?”

No. An inactive user cannot sign in, and a fieldworker submits claims in the app — so nothing new can come from them. Claims they already filed are unaffected and still go through approval and payment. See making someone inactive.

Make them Inactive instead. They cannot sign in, they drop out of the list, and their jobs, hours and payment history stay where they are. See making someone inactive.

Somebody has left — what happens to the jobs still on them?

Section titled “Somebody has left — what happens to the jobs still on them?”

They become unassigned. The work is not cancelled and not deleted; it just has nobody on it, and it appears in the unassigned list on the scheduler waiting for a name. Reassign each one to another fieldworker, or mark it complete, cancelled or closed if it is no longer happening.

A fieldworker can see something they should not

Section titled “A fieldworker can see something they should not”

Their permissions are on their own record, under Fieldworker Mobile app permissions — untick the line and Update. If it should be hidden from every fieldworker, it belongs in Settings → Mobile App instead. See fieldworker mobile app permissions.

No. It records that a payment has gone out, so the period stops showing as Unpaid. Pay the person however you normally do. See paying a user.

Can I change a period after finalising the salary?

Section titled “Can I change a period after finalising the salary?”

Finalising moves the period to Payment History as a settled record. Get the attendance right before you finalise, because the calculation is only as good as the check-ins behind it. See finalising the salary.

They can change their own — see changing your password. A new password can also be set for them from Edit User.