TeamTime - Summary Web Part

A summary web part is available that can be put outside a TeamTime site that will display a summary of un-approved, missing or under-time timesheets.

This web part can remind users to complete or approve their timesheets by being placed on an often visited page like a portal home page.

In this example we can see that the current user

  • Has an approved timesheet for the week starting on the 24th March, but its only got 30 hours on it.
  • Has a timesheet for the week starting the 31st March with 5 hours and is not yet approved
  • Doesn't have any timesheet for the week starting 7th or 14th April.


Note - this feature was added in version 2.1, April 2014.

How to add to a page

  • Put the page into Edit Mode
  • Put the cursor where you want the web part to be
  • On the ribbon click Insert then Web Part
  • Choose the TeamTime category then "TeamTime - Timesheet Summary"
  • Click Add


How to configure

Open up the web part in configuration mode by

  • Clicking on the link after you added it or
  • Put the page in edit mode, click the web part menu (top right of the web part) and select "Edit Web Part"

You will configure the web part for use by all visitors to the page you've put it on - it will pick up the current user and only display their own records.

In the first box put the full URL's of any TeamTime sites you want the web part to check. If the visitors to the page that you've put this summary web part on can put their Timesheets in several different sites then you may have multiple entries here each on their own line.

(If the current user doesn't have access to a TeamTime site no error will be displayed - it just won't search that site. In this way you can put multiple sites in here and the summary web part will respect the security setting you've got set-up in SharePoint).

Look back X weeks - Specify how many weeks the summary web should look back.

Show missing timesheets - if you want the web part to display a warning if there are no timesheet for a week.

but only for users in user setting list - If you've got multiple sites listed and you are NOT using site specific permissions to limit access you may only want to display missing timesheet warnings where the user has an entry in the TeamTime users list otherwise it will display warnings about missing timesheets in every site in the list that the user has access to.

Show unapproved timesheets - display a warning about any weeks that have timesheets left unapproved. This is especially useful if you've set users up to approve their own timesheets.

Show approved timesheets with low hours - approved timesheets are normally hidden from the user list but this feature lets you display a warning if they have a low number of hours. E.g. the Working Hours for the site or user is set to 8 hours for 5 days (40hrs a week) then this will display a warning if the total hours for this week is below this.


How to customise the appearance

If you are familiar with Cascading Style Sheets (CSS) you can customise the appearance of the summary web part.

Use your browsers developer toolbar to examine the summary toolpart table and the .CSS file plt-summary-webpart.css which contains comments for different CSS selectors and how they are used.

You can then use the Content Editor web part in SharePoint 2010 or the Script Editor web part in SharePoint 2013 to add a .CSS file to the page and override the existing one.

For example the "Missing" timesheets are shown in red. If you wanted to make it bold and a larger text you could use

/* For Missing timesheets */
 TABLE.plts-summary TD.plt-status-missing {


Performance implications

Although there is no limit on the number of sites you can ask the summary web part to search you should consider performance, especially if this will be used on a high-traffic page such as a portal home page.

If there are too many sites to search (or perhaps only a minority of users actually use a TimeSheet) then you should consider creating several summary web parts on something like a departments home page - for example one on the Engineering and another one on the Finance home pages. In this way it will get less traffic and have to search less sites.