Staff Details Fields and Buttons

Use the fields and buttons on the Staff Details pane to enter/display user/resource setup and permissions information for a selected employee.

Field Description
First Name Enter the employee first name or a name for the generic resource. This field is mandatory.
Last Name Enter the employee last name.
Location Select the employee / generic resource location. This field is mandatory for both employee and resource.
Department Select the employee / generic resource department. This field is mandatory for both employee and resource.
Email Address Enter the employee email address.

This field is mandatory for both employee and generic resources, although for generic resources, you can enter a "fake" email address.

An employee email addresses must be the user's valid email address.

Telephone Number Enter the employee contact number.
Mobile Number Enter the employee cell phone number.
Cost Per Hour Enter a cost per hour. If you set this field to zero, profit reporting does not take employee costs into account as business costs on jobs and projects. Only external purchases and expenses are displayed as "costs" throughout the TrafficLIVE system.

Adding a value to this field at a later stage does not change historical entries, therefore the decision that you make at implementation should be carefully considered.

If values are set here, there are user permissions that you can set to ensure that only the appropriate staff members have access to this information.

External User Code If you are integrating TrafficLIVE with another system and employee details need to match, you should enter the appropriate employee number or code from that system in this field in TrafficLIVE.
Personal Rate Charge Band Select the employee's personal rate charge band. You also need this for a generic resource if you want to use the generic resource for estimated costing. Click Clear to clear the selection.

This sets the rate that TrafficLIVE uses when you bill in accordance with the person who is working on a task, regardless of the activity he or she performs.

The majority of agencies sell services based on activity. For example, an agency may sell web design work at $100/hour. If a junior web designer does the work, the agency may make more money (or may not, because the work may take him or her longer). If a senior designer does the work, the agency may make less money; but again, a senior designer may complete the work more quickly.

Some agencies sell work based on who actually does the work. Using the previous example, a Junior Designer may have a sell rate of $90 per hour, whereas a Senior Designer has a sell rate of $150 per hour.

TrafficLIVE calls this Costing to Allocated Resource. This is a mode that you can select by default in the Admin section or on a job-by-job basis.

Even if you do not use Costing by Allocated Resource, it is useful to set this value against an employee to report and track whether the appropriate person/role worked against the predefined job activity.

The charge band rates are set in Admin > Charge Bands.

Expected Daily Hours to be Logged Enter the number of hours per day that you expect the employee to log. This is used for capacity management.
Expected Daily Hours to be Logged (Billable) Enter the number of hours per day that the employee works that you expect to be billable.
Create Account OR Create Generic Resource Click Create Account to create a user account.

Click Create Generic Resource to create a resource account.

TrafficLIVE allows you to add resources to the system so that you can manage them effectively. Resources can include rooms, projectors, or generic roles such as "Designer" if you want to portion or cost work but do not yet know who is going to do it.

Resource users are only available to users of the TrafficLIVE Enterprise plan. Resource users carry no fees, cannot log in, and are only visible in selected views.

If you create a resource as a generic resource, you cannot change it to a user.

These options are disabled (grayed out) until you click Add User, enter the relevant details, then click Save.

Account Details

Field Description
User Name This field displays the employee's username.
Enabled This field displays True if the user account is enabled and False if it is disabled.
Account Locked This field displays True if the account is locked and False if the account is not locked. An account might be locked after multiple failed login attempts or if the Admin has clicked Lock.

Click Lock to lock the account, meaning that the user cannot access TrafficLIVE. Click Unlock to allow the user to access TrafficLIVE.

Single Sign On This field displays True if the account has single sign-on enabled and False if it is not enabled.

To use single sign-on, you must set up your credentials in the Admin section of TrafficLIVE and add TrafficLIVE's metadata to your Id.

Last Login This field displays the date when the user last logged in to TrafficLIVE.
Traffic Admin Select this check box if you want this user to be able to add users and edit user permissions.
API Token If you clicked Generate API Token, this field displays the token details.

Account Actions

Field Description
Click to reset the user's password.
Click to disable or enable the user's account. The Enabled field displays True if the user account is enabled and False if it is disabled. A disabled account is no longer recognized as a paid-for license.

When you disable users, they are locked out of TrafficLIVE, and they cannot be used as resources. A disabled user appears as disabled in all historical data and other existing records at the time that the user is disabled.

Click Lock to lock the account, meaning that the user can no longer log in to TrafficLIVE. Click Unlock to allow the user to log in to TrafficLIVE. The account is still counted as a paid-for license.

Account Locked displays True if the account is locked and False if the account is not locked.

Click to generate an API token for integration with third-party systems.
SSO Enable After you have enabled single sign-on (SSO) in TrafficLIVE, click this button for each user who will authenticate using SSO.
  • After you set a user up for SSO, he or she cannot log in via the standard TrafficLIVE login method.
  • A disabled TrafficLIVE user who has SSO enabled cannot log in to TrafficLIVE.
  • A user who is locked in TrafficLIVE can still log in with SSO because a lock only applies to the TrafficLIVE login service. Organizations that use SSO authentication should lock users in their identity provider.