Best Practice: Onboarding a New Tenant
Most of the trouble in a new MSP Pulse tenant comes from setting things up in the wrong order. Nothing breaks outright. The pay calendar quietly lands a pay run on a bank holiday, an engineer gets invited before the labour roles exist so has nothing to log time against, or the SLA clock counts hours your team never works. Each one is easy to fix once you spot it, and easy to miss for weeks first.
This guide gives you a setup order where each step has what it needs from the one before. It starts with enrolling your first device on Secure Access, which a new company must do before anything else, then the AI-guided setup, which covers the next few steps for you, and moves through the settings that make the calendar, leave, timesheets and payroll behave.
1. Set up Secure Access and enrol your first device
Secure Access is not optional. It is how MSP Pulse protects your company's data: it can only be reached from devices you have enrolled, over a private network. The sign-in page stays public, but there is no public route to the data behind it.
That is why a new company's access is restricted from the start. When the owner first signs in, they are taken to Secure Access and asked to enrol a device before anything else. Until a device is enrolled and connected, the rest of MSP Pulse stays locked, so the guided setup and the settings in this guide wait until it is done. Do it first, and do it properly, because everything else in this guide is built on it.
The steps are:
- Install the PON Agent on your own computer. Go to
app.msp-pulse.com/agent. It detects your operating system and offers the right installer (Windows, macOS or Linux). You can download it without signing in because it does nothing without an enrolment code. Phones and tablets use a QR code instead, shown on the same Secure Access page. - Get an enrolment code. In Settings → Organisation → Secure Access, choose Enrol a device. You get a short single-use code. Run the PON Agent, type the code in, and restart the computer if the installer asks you to.
- Check the status chip. Back on the Secure Access page, the chip should read Connected to Secure Access. That chip is the real test. The agent's own tray icon only tells you it is running, not that your traffic is going over the private network.
- Carry on over Secure Access. Once your device is confirmed connected, Secure Access takes effect and the restrictions lift. From here on, sign in to MSP Pulse from the enrolled computer.
Why first. Do this before anything else, and before inviting anyone, so each person only has to do it once. Every invitation email carries the PON Agent download link and the enrolment steps. A team member cannot sign in until they have an enrolled device, so after inviting them you generate their first enrolment code yourself, under Enrol a team member's device on the same Secure Access page, and send it to them securely. They install the agent, enter the code, and they are in. If you invite people before you have enrolled yourself, you cannot do this for them, and the whole team waits on you. A second device for the same person waits as pending until an owner or admin approves it, which is intentional.
Three things to know before you start:
- Do the first device on a computer you control and will keep. If your only enrolled device is lost, you will need MSP Pulse support to recover access, and they will want to verify who you are first. Enrol a second device early.
- Turn off your browser's secure DNS (DNS over HTTPS) on enrolled computers, and Private DNS on Android. These send name lookups around Secure Access, and the usual symptom is a page that simply won't load. Your company's secure address only opens with
https://in front. - If you use a DNS filter or a VPN on the same computer, check the guidance on the agent download page before you rely on it. A full-tunnel VPN in particular can stop the two working together.
2. Run the AI-guided setup
Once your device is connected, MSP Pulse offers a guided setup: a chat with an assistant that asks you questions and prepares the settings for you. It currently covers five things, in this order:
- Locale. Country, currency, timezone and date and time format.
- Company. Your company details, which appear on invoices, quotes and emails.
- Labour roles. The roles you bill time under, such as Engineer or Consultant, their rates, and optionally location and time modifiers (onsite, remote, after hours).
- Outbound email. How customer-facing email (invoices, quotes, ticket updates) is sent.
- Inbound email. The mailbox that turns incoming mail into tickets.
The assistant works on an assist-with-confirm basis. It proposes a change, you see it on a confirmation card, and nothing is saved until you approve it. Treat each card as a draft to read, not a button to click through. This is especially true of rates: the assistant can suggest sensible roles and modifiers, but only you know what you charge.
You can pause and come back. If you skip the setup or leave halfway, it isn't lost. Go to Settings → Company and use the Guided setup card to continue or restart it. Nothing you have already saved is undone by restarting.
The guided setup is deliberately short. It gets billing and email working so you can start. Everything below is what you set up next, and it matters just as much, because the assistant doesn't ask about it.
3. Set your working week and business hours
Go to Settings → SLA. This is where you set:
- Business hours, the start and end of your working day.
- Working days, shown as day buttons. Blue days are working days and the rest are your weekend.
- Week start, using the arrows beside the day buttons. A Sunday-to-Thursday week is as easy to set as Monday-to-Friday.
Do this early because several later things depend on it. The SLA clock uses these hours for P2 to P4 tickets (P1 counts 24 hours a day). The Calendar starts its week on the day you choose here. And the pay calendar in Section 5 uses your working days to decide when a pay run can fall.
If you want MSP Pulse to choose between office-hours and after-hours labour rates from the clock, the Office-hours rates card on the same page does that, using these business hours. It needs your labour roles to have both an office-hours and an after-hours rate, so come back to it once you are happy with your roles. If you would rather engineers pick the rate themselves, leave it on manual.
4. Add your public holidays
Still thinking about days off: add your National Holidays. They sit in Settings → Finance → Payroll. Use Add National Holiday for each date and name it.
They are not set up for you, so each year you will need to add them. Do it now, because holidays feed three things:
- The calendar shows them, so nobody schedules a visit on one.
- With office-hours billing on, a holiday counts as after-hours all day.
- The pay calendar moves a pay run or submission cutoff that falls on a holiday back to the previous working day.
That last one is why holidays come before pay periods. Generate the pay calendar first and add holidays afterwards, and the dates will already have been calculated without them.
5. Set up your payroll schedule and pay periods
Still in Settings → Finance → Payroll, create a payroll schedule. It describes how often you pay people:
- Frequency: weekly, fortnightly, four-weekly or monthly.
- Period start date: the first day of the first pay period (not the day people are paid).
- Pay run day and submission cutoff day: for weekly-style schedules these are days of the week, for monthly ones days of the month. The cutoff is the last day expenses and overtime can be submitted for that period.
Then open the schedule's Pay calendar and add a pay year. A pay year doesn't have to be a calendar year, so use whatever window your payroll runs on. Choose Preview periods before saving. This is the review step: you see every period with its pay run and cutoff date, and a marker beside any date that was moved to the previous working day because it landed on a weekend or holiday.
Two things worth knowing:
- MSP Pulse does not store pay rates or salaries. Those live in your payroll software. MSP Pulse produces the variable-pay pack (hours worked, leave, overtime hours, expenses and mileage) for whoever runs payroll. This is deliberate, to keep sensitive pay data out of the platform.
- The hours come from the schedule, not from logged time. Someone contracted for 8 hours a day is reported at 8 hours a day. Time logged to tickets and the time clock are separate measures and don't change what the pay pack reports.
6. Invite your people
Now that labour roles, working hours, holidays, a pay schedule and Secure Access are in place, invite the team. Go to Settings → Users and use Invite. Each person gets an email, sets their own password and sets up TOTP before first sign-in. The email also explains how to get their computer enrolled, but they need an enrolment code from you (Section 1) before they can use it.
Choose an Access Role for each person, in Settings → Access Roles. The owner or admin has full access. Other people get exactly the sections their role grants, and the seeded Engineer role covers day-to-day work such as the service desk, projects, calendar, clients, quoting and invoicing. Create narrower roles before you invite anyone who should see less, because it is easier to start with the right role than to remove access later. Note that Settings is one section: anyone with it can change any setting.
Then open each person's Employment tab (owner and admin only). This is where the earlier steps pay off:
- Pay schedule: pick the schedule from Section 5. Only people assigned to a schedule appear on its pay reports.
- Working week: the days and hours they work, with an unpaid break per day. The daily hours are the day's length minus the break, and the weekly total updates as you type.
- Normal hours per week and whether they are eligible for overtime. Overtime can only be resolved as paid overtime for eligible people.
- Payroll reference: the ID your payroll software uses for them, which keeps the pay pack easy to match.
- Labour roles: which roles they can log time against, and which is their default. Someone with no roles assigned can use any role, so assign them as soon as you know who does what.
- Schedule type: Fixed weekly uses the working week above. Variable rota is for people whose hours change week to week, set on the rota instead.
7. Check the calendar and leave
By now the Calendar already shows each person's working hours, your public holidays, and any approved leave. Check it before the team relies on it. Open a few people's weeks and confirm the shaded non-working hours match what you meant.
For leave, the standard types (Vacation, Sick, Study Leave and Unpaid Leave) are already there. People request leave from their own Leave tab and an owner or admin approves it. Approved leave appears on the calendar and is taken out of the hours reported to payroll.
If your engineers use Outlook or Google Calendar, Settings → Service Delivery → Calendar Sync can push scheduled work into their own calendars. It is optional and off by default, and each company registers its own app with Microsoft or Google, so leave it until the basics are working.
8. Decide on the optional extras
These are all off or empty by default for a new tenant. Turn on only what you will actually use.
- Timesheets. Lets engineers review and submit their pay-period timesheet for approval. Off by default for new tenants. Turn it on once pay periods and schedules are in place, because without them there is nothing to submit.
- Time clock. A clock-in and clock-out record for people who need one. It is an attendance aid and doesn't change pay. You can exempt salaried staff from it.
- TOIL policy. If you give time off in lieu, decide whether it expires and whether there is a cap before the first engineer earns any. The policy is in the Payroll settings.
- Travel and mileage. Under Settings → Finance → Travel & Expenses: whether you charge clients for travel time, your mileage rate for engineers using their own vehicle, and whether expenses are recharged. Mileage is reimbursed through payroll and never charged to the client.
- Accounting integration. Connect Xero or QuickBooks Online and choose your account codes. See the guide on account codes before you do.
Pre-flight checklist for a new tenant
- [ ] Secure Access done first: PON Agent installed on your own computer, status chip showing Connected, and a second device enrolled
- [ ] Browser secure DNS turned off on enrolled computers
- [ ] Guided setup completed (locale, company, labour roles, outbound and inbound email), with every proposal read before approving
- [ ] Rates confirmed by a person, not accepted because the assistant suggested them
- [ ] Business hours, working days and week start set in Settings → SLA
- [ ] Public holidays added for the current year (and a reminder set to add next year's)
- [ ] Payroll schedule created with the right frequency, period start, run day and cutoff day
- [ ] Pay year previewed, with any moved dates checked, then saved
- [ ] Access roles created for anyone who should see less than the Engineer role
- [ ] Team invited, with each person's TOTP set up
- [ ] Each person's Employment tab filled in: pay schedule, working week with breaks, hours per week, overtime eligibility, payroll reference
- [ ] Labour roles assigned to each person, with a default
- [ ] Calendar checked for a few people: hours, holidays and leave all showing correctly
- [ ] Timesheets, time clock and TOIL turned on only if you will use them, with the TOIL policy decided first
- [ ] Travel, mileage and expense settings reviewed
- [ ] A test ticket, time entry and (if relevant) timesheet run through end to end before real work starts