Support
OneShift Workspace guide
Workspace managers shape what everyone else logs time against: the workspace settings, the project templates, the customers, projects and tasks, and the budgets on top of them. This guide walks through each, in the order you usually set them up.
Everything here lives under the Manage group in the sidebar, which only workspace managers see. The exception is Branding (email signature and profile page): it sits in the same group but needs the separate Branding permission.
Workspace settings
Workspace → Settings, annotated. There is no Save button: text and time fields save when you leave them, switches and dropdowns save at once, sliders save when you let go. A “Settings updated” toast confirms each save. Hover a pin or a note to connect them.
Workspace
How many hours an employee is expected to log per day.
When to send start and end of day notifications to employees.
How reports, statements, and exports show durations
Timesheet review accuracy
Below the settings, workspace managers see a “Timesheet review accuracy” panel covering the last 90 days. It reports, per verdict, how many reviews were computed and how many of those timesheets were later changed — rejected, or an entry edited by an approver after the review — for example “Looks good — 40 reviewed, 3 later changed (8%)”. It also shows how many suggested changes were offered and how many approvers applied. Until a review exists it reads “No timesheet reviews in this period yet.”
Project templates
Workspace → Templates. A template is a project blueprint: a name, a description, a budget, the task-less logging switch and a list of tasks. Pick it when creating a project and the whole structure is copied in one go.
- Budget
- Fixed · 10d
- Time without a task
- allowed
Tasks
- Development
- Design review
- Internal sync
- Customer
- Contoso
- Budget
- Fixed · 10d
- Time without a task
- allowed
Tasks
- Development
- Design review
- Internal sync
- 1Add template Name (2–100 characters), an optional Description, a Budget (type and amount) and the switch “Allow logging time without a task”. Create opens the template’s own page.
- 2Fill in the tasks On the template page, Add task takes a Name, Description, and the three switches Active, Billable and Exclude from utilization, plus an optional Budget. Edit or delete a task from its row menu.
- 3Rename or retune later The details card saves each field on its own — Name and Description when you leave them, Budget when the type changes or the amount loses focus. Toast: “Template updated”.
- 4Apply it In “Create new project”, the Template dropdown appears as soon as one template exists. Choosing one hides Name, Description and Budget — they come from the template. Only Customer, Public project and the task-less switch stay editable.
Customers
A customer owns projects, and through its contacts it owns the portal access. Nothing else is stored on it — no address, no currency, no billing email. The tree below is what archive and delete walk.
- ProjectWebsitePublicDevelopmentQAAdmin
- ProjectMobile appDiscoveryNo task — log on the project
The list
- Create customer asks only for a Name (2–100 characters) and an optional Description. The description feeds the AI suggestions, nothing else.
- Search and “Show archived” are the only filters. Archived customers render struck through.
- The row menu holds Edit, Archive or Unarchive, and Delete. These are the only places to archive or delete — the detail page has neither.
The customer page
- Projects — the same project table and Create project dialog as the Projects page, minus the Customer field.
- Contacts — the people who sign in to the customer portal. Each contact has a Name, an Email and a Permissions grid: one Board switch and one Statements switch per project. A new contact starts with everything off. “Send portal login link” mails them a sign-in link.
- Suggestions — AI findings about unclear names and descriptions. A description you saved from a suggestion as it was proposed is not flagged again until you change the name or the description.
- Settings — Name, Description and External number, the customer’s id in your invoicing system. Each saves when you leave the field.
delete before the button enables.
Projects
A project belongs to one customer and is what members pick time against — directly, or through its tasks. The “Create new project” dialog, annotated; the same fields live on the project’s Settings tab afterwards.
🪄 Used for AI assistance.
The project page
- Tasks — the task table and dialog, next section.
- Users — who may log time on a private project. Add a user from the picker; “Make lead” marks a project lead, shown next to the project name. Public projects need no user list.
- Checklists — recurring checklists tied to tasks, with the members who receive them.
- Settings — Name, Customer, Description, Public project, Allow logging time without a task, Budget and Prepaid. Every field saves on its own, toast “Project updated”. Changing Customer moves the project, with all its tasks and time, to another customer.
- Board — the issue board under the tabs, shaped by the Issue Workflow.
Tasks
Tasks live on the project’s Tasks tab. They decide whether time is billable and whether it counts toward utilization — the two flags members cannot override.
| Name | Active | Billable | Utilization | Budget | Total time |
|---|---|---|---|---|---|
| Development | Active | Billable | Utilized | Fixed13d / 20d | 13d |
| QA | Active | Billable | Utilized | Monthly4d / 3d | 4d |
| Discovery | Inactive | Non-billable | Utilized | 2d 4h | |
| Admin | Active | Non-billable | Excluded | 2d 4h |
“Create task” / “Update task”
- Name (2–100 characters) and an optional Description.
- Active — on by default. An inactive task leaves every member’s task picker and its checklists stop, but the task and its time remain visible here and in reports. Use it to retire a task without archiving it.
- Billable — off by default. Only time on billable tasks is invoiced, counts toward budgets, and feeds the Billable gauge.
- Exclude from utilization — for leave, admin and the like. Logged and reported, ignored by the gauges.
- Budget — type and amount, see section 06. Tasks have no Prepaid switch.
- Starting balance — time tracked before this task existed in OneShift, with the date it was carried over. Set both or neither. It counts toward the task budget and total.
How members see them
- BillableEntries get a green tint in the timesheet grid and the Billable switch in the Details dialog.
- Non-billableInternal work. Counts toward total utilization only.
- Excluded from utilizationLogged and reported, but neither gauge counts it.
Members only see tasks that are active, not archived, and sit on a project they can log on. Time logged without a task shows as “No task” under the project.
delete, and then removes the task with every
time entry and statement entry on it. Archive or deactivate instead when the time should
survive.
Budgets
A budget is an amount of time, set on a project, on a task, or on both. The two levels are independent: the project budget does not cap its tasks and task budgets are not summed into it.
The Budget field
One input with a type dropdown attached: None, Fixed, Monthly or Annual. The amount follows the workspace time unit — in Days a plain number is days (1.75 or 2d 3h 40m), in Hours it is hours (10, 10:30 or 10h 30m). A grey hint shows how it was read. Choosing None clears the amount and removes the budget; any other type with an empty amount is refused: “Budget amount is required when a budget type is set.”
| Type | Meaning | Window |
|---|---|---|
| None | No budget. The amount field is disabled and the bar disappears. | — |
| Fixed | One pot, consumed from the first entry ever logged. | all time |
| Monthly | A fresh allowance every calendar month. | 1st – last day of month |
| Annual | A fresh allowance every calendar year. | Jan 1 – Dec 31 |
What a window means
The dark line is today, early October. Only Fixed reaches back before January.
What counts as consumed
- Billable time only. Non-billable entries never touch a budget, whichever task they sit on.
- Everyone’s time. The bar splits into the viewer’s own share and the rest of the team, but the total is the whole project or task.
- Starting balances on a task count as consumed from day one. They are nobody’s logged time, so the split bars show them under “Team time” or “Others”.
- Monthly and Annual reset. Those bars count only the current month or year — today’s on the Projects list, the customer page and the project page; the week’s on the Timesheets and approval screens; the report’s start month or year on the Customer report. Fixed counts everything ever logged.
The bar, as members see it
Dark is the viewer, light is everyone else. Past the budget the bar and the “used / total” figure turn amber and the card says how far over it is. On the Timesheets page the split reads “My time” and “Team time”; on an approval page it is the owner’s name and “Others”; on the Customer report it is “Current report” and “Previous reports”.
Prepaid
Prepaid turns a project’s Monthly or Annual budget into an allowance the customer has already paid for. A statement then bills only the time above it. Below, a statement for a 5-day monthly retainer where the team worked 5 days and 2 hours.
Current 5d 2h · Previous 0
Prepaid budget covers 5d. Only the 2h above budget are billed (€200.00), instead of the gross €4,200.00.
- Development€160.004d 2h—
- QA€40.001d4h
Switching it on
The Prepaid switch sits under the Budget field on the project’s Settings tab and in “Create new project” — “Treat budget as a per-period allowance (Monthly / Annual only).” It stays disabled while the type is None or Fixed, and changing the type back to one of those clears it. A one-off prepaid block is not supported: the budget must be a recurring allowance. Tasks and templates have no Prepaid switch.
What it does on a statement
- 1The allowance is frozen at first capture When the project’s time first lands on a statement, that statement keeps a copy of the budget, its type and the Prepaid flag. Editing the project afterwards changes future statements only — approved figures never move.
- 2Covered time comes off the top Billable time on the statement up to the allowance is covered. Only the remainder is priced: the totals show a Prepaid pill, the covered amount, and a note — “No additional charge for this statement.” or “Only the … above budget are billed …”. A prepaid project with no billable time on the statement still shows the pill, the full allowance and the note “Nothing to bill on this statement. No additional charge.”
- 3The customer sees the same The portal and the Excel export show identical coverage, with PREPAID DAYS and BILLED DAYS rows (HOURS in an Hours workspace), in review and after approval. With no billable time the export still deducts the PREPAID DAYS and shows BILLED DAYS 0 and AMOUNT 0.00.
If you change a prepaid project’s budget while a statement is still open, the statement shows an amber warning, “Project budget settings changed since this statement was created.”, on the list and on its page. Nothing re-bills on its own: re-capture the time if the new allowance should apply. Approved statements never show the warning. How statements are built, reviewed and invoiced is in the Billing guide.
Email signature
Branding → Signature. One email signature for the whole workspace, written once as an HTML template. Every member gets their own copy, filled in with their details. Branding needs the Branding permission (branding:manage), granted through the workspace's roles and separate from workspace management.
- One signature per workspace. Save stores it; clearing the editor and saving removes it. Nothing is saved until you press Save.
- Fields. Click a field above the editor to insert it where the cursor is:
{{fullName}},{{jobTitle}},{{email}},{{phone}},{{pictureUrl}},{{profileUrl}},{{linkedInUrl}}and the others listed there. Wrap a block in{{#if phone}}…{{/if}}to show it only when the member has that value. For a call link use<a href="tel:{{phoneUri}}">{{phone}}</a>, where phoneUri is the phone number reduced to a leading + and digits, with no spaces or punctuation.{{position}}is the billing position, not the job title; use jobTitle in a signature. - Edited as HTML. Signatures are designed in an external editor and pasted here as HTML source. Tables, inline styles and image links are kept exactly as pasted.
- Preview per member. The preview shows the unsaved signature for the member you pick, the current user by default. A mistake such as an unknown field or a template syntax error is shown under the editor, and a signature with such a mistake cannot be saved.
- Job title and Phone. Members have neither by default. Set them in the Job title and Phone fields on their Member Settings page. Members can also enter their own phone and LinkedIn link under Account → Contact details, and you can set a member's LinkedIn link on the same page.
- Two signatures. The Signature tab has a toggle: New messages is the main signature, and Replies & forwards is an optional second one, usually shorter. Each has its own editor, preview and Save button. The reply editor has a Start from main signature button that fills it with the saved main signature, ready to trim; it asks before replacing what is already there, and nothing is saved until you press Save. Without a reply signature, the main one is used everywhere. Switching between the two asks before discarding unsaved edits.
- Getting it into Outlook. Members don't copy the signature themselves. Once your Microsoft 365 admin deploys the OneShift add-in for Outlook, it inserts the signature automatically: the main one on new messages, the reply one on replies and forwards (or the main one when there is no reply signature). It is filled in when the message is written, so changes to a member's phone, job title or photo, and to the template, show on their next email.
- Deploying the add-in. A Microsoft 365 admin opens the Microsoft 365 admin center → Settings → Integrated apps, uploads the OneShift add-in package, assigns it to everyone (or to chosen users and groups) and accepts its permissions. It can take several hours to appear in every mailbox. The workspace's Microsoft connector must be linked to the same Microsoft 365 tenant, because that is how the add-in matches each mailbox to a member.
- Log time from Outlook. The add-in also adds a Log time button to the ribbon when you read an email. It opens a pane to log time to OneShift for that email, in Outlook on the web, new and classic Outlook for Windows and Outlook for Mac, but not on mobile. The pane pre-selects a customer, project and task from the customer contact whose email is the sender or a recipient, else your most recent time entry, else your default task, and says why it picked it; you can change it. The comment starts as the email subject without any RE: or FW: prefix, and you can edit it before saving; whether a comment is required follows the workspace setting. The date defaults to today and the duration to 15 minutes (presets 15, 30 and 60 min), entered as HH:MM like on the timesheet, and Billable follows the task. Only active, non-archived projects and tasks you can log to are offered, and the same rules as the timesheet apply: submitted or approved weeks can't take new time, your working period applies, and a project that requires a task needs one. Admins: the add-in must be deployed again after this update for the button to appear.
- Public profile. Members can turn on a public profile page under Account → Public profile and copy its link. The page shows their photo, name, job title and workspace, with Call, Email and LinkedIn buttons, a Save contact button and a QR code, and anyone with the link can open it. {{profileUrl}} is that link and stays empty until the member turns their profile on; {{linkedInUrl}} is the LinkedIn link from their Contact details. You can also turn a member's public profile on or off with the Public profile switch on their Member Settings page. The page is hidden, whatever the switch says, while the member is inactive or their working period has ended.
Profile page
Branding → Profile. One template for every member's public profile page, written once as HTML. Without a template, members get the built-in profile page.
- One template per workspace. Save stores it; clearing the editor and saving removes it, and the built-in page is used again. Nothing is saved until you press Save.
- Same editor as the signature. Click a field above the editor to insert it, and pick a member to preview the unsaved template as that member's page. The fields are the signature fields plus
{{qrCodeUrl}}, the QR code image for the member's contact card (use it as an image source), and{{saveContactUrl}}, the link that downloads their contact card (use it as a link target). - Members still turn it on. A member's page is only public once they turn on their public profile under Account → Public profile. The template changes how the page looks, not who is published.
- Scripts never run. The page is shown without any script, so buttons that need JavaScript do nothing. Use links and images instead.
Audit log
Every change to your workspace data is recorded: what changed, who did it and when. Anyone who can open an item can read its history; workspace admins also get one page with everything.
Where History appears
- History tab. Projects and customers have a History tab, the last one. The Workspace page has one too, for workspace admins.
- History button. The Team page, member pages, team pages, project templates, statements and timesheets have a History button in the header that opens a side panel. On your own Timesheets page, each saved week has a History button that opens the same panel.
- Same access as the page. If you can open an item you can see its history; there is no separate permission.
What is recorded
Creating, updating, archiving and restoring, activating and deactivating, and deleting customers, projects, tasks, contacts, project members and rates. Workspace settings, including connectors, positions, teams, project and task templates, and member role and permission changes. Statements: creation, status changes, invoice fields, entries added, removed or edited (including the bulk actions applied factor, cut off billable time, reset to baseline and split) and statement contacts. Timesheets: submit, approve, reject, reopen and delete, plus time entry changes. Changes to tasks, entries, project members, rates and task templates show on their parent: the project, statement, timesheet or project template. Issues keep their own existing history and are not part of this log.
What each History view shows
A History view shows the item itself plus the changes of parts that have no page of their own.
- Workspace: workspace settings, the email signature, the profile template, connectors and positions.
- Billing rates page: rate and currency changes across workspace, positions, projects and project-position rates.
- Team page: member, team and team membership changes across the workspace.
- Customer: the customer, its contacts and contact permissions.
- Project: the project, its tasks, project members and rates.
- Project template: the template and its task templates.
- Statement: the statement, its entries and statement contacts.
- Timesheet: the timesheet and its time entries.
- Team: the team and its team members.
- Member: the member only.
Reading an entry
Each entry has a sentence describing the change, an action pill, and the time — relative, with the exact time on hover. Expand it to see the field changes as “Field: old → new”. The actor is a workspace member, a portal contact, the Teams bot acting for a member, a member working through a connected AI tool (shown as “Maria Ivanova via AI tool”), or “System” for scheduled jobs. Entries that come from one action are grouped: capturing 200 entries into a statement shows as one event you can expand. Older entries load as you scroll down. An item with nothing recorded shows “No changes recorded yet.”
The Audit log page
Audit log, under Manage (/audit), is for workspace admins only and lists all events. Filter by object type, object (search by key or name), actor, action and date range. The object type, actor and action filters are searchable: open one and type to narrow the list. One actor filter covers members, portal contacts, the system, the bot and AI tools. Clear filters resets them. Click an actor to filter by that person, or the filter icon next to an object to see its full trail. Move through the log with Previous and Nextand choose how many rows each page shows (25, 50 or 100). Changing a filter returns to the first page.
How long history is kept
The retention period is set by the workspace operator: 90 days by default, and a year for workspace settings, member, statement and timesheet changes. Whatever the period, the 10 most recent changes of every item are always kept, so a rarely edited item never loses its trail.
Seniority
Team → Users shows a Seniority column, and each member's Member Settings page has a Seniority card. Seniority tells OneShift how much training time to expect from that member on each new project.
- What it changes. Seniority sets a training allowance on each new project the member works on. The allowance starts at a share of the week and falls to zero over a ramp-up period: Intern 50% falling to zero over 12 weeks, Junior 30% over 8 weeks, Mid 15% over 4 weeks, Senior 5% over 2 weeks, and Lead none. The timesheet review uses it to suggest marking time as training. Members without a seniority get no training suggestions.
- Who sets it. Workspace admins, HR managers and team leads choose the value in the Seniority select on Member Settings (Intern, Junior, Mid, Senior or Lead, or “Not set”); it saves at once and a “Seniority updated.” toast confirms it. Members never see their own seniority.
- Training. Below the select, the card lists each project the member has trained on: its state (Improving, Stalled, Done or Not enough data), the week of the ramp-up (for example “week 3 of 8”) and how the training share moved (for example “40% → 15%”). Until there is any, it reads “No training recorded yet.”
- History. Changes to the seniority appear in the member's History.
- HR permission (hr:manage). Granted through the workspace's roles and separate from workspace management. It opens Team → Users and every member's Member Settings page, where all fields can be edited. The Teams, Positions and Access & Roles tabs and the rest of Manage still need workspace management.