Skip to content

Trust starts with clear answers

Your people. Your setup. Questions worth asking.

Before a team introduces employee information, it needs to understand access, data handling and the scope of the service. Here is how Shift Hub approaches a supported pilot and what we review together.

01 / SETUP & ACCESS

Personal sign-in and role-based access

Employees use individual accounts. Server-side permission checks separate employee actions from manager and owner actions. Time-record approvals require an independent reviewer. Within a company, current manager roles operate across the configured operation; location-by-location manager restrictions are not a general capability today.

02 / SETUP & ACCESS

A separate setup for each new company

A supported company pilot is set up separately from other companies, with its own application and data. Company identity is checked before workspace use. Before onboarding, we review who needs access, which locations belong together and whether the proposed setup supports your requirements.

03 / SETUP & ACCESS

Employee information deserves a clear purpose

Time records and scheduling data support the working day. Location checks around clock actions help identify entries that need review. Discuss the required permissions and the information your staff should receive before enabling a workflow. The demo inquiry form is for business contact details, not employee or payroll records.

04 / SETUP & ACCESS

Know what needs agreement before rollout

The setup discussion must cover data hosting, access, retention, backups and recovery, support and service terms. These need to be appropriate for your business before employee information is introduced. This public overview is not a security certification or a substitute for an agreed service or data-processing arrangement.

05 / SETUP & ACCESS

Validate the handoff before using pay outputs

Scheduling and time-record review are separate from running payroll. New pilots keep payroll approval and exports disabled until their company-specific pay rules and handoff are validated. Shift Hub does not promise statutory payroll compliance, calculate deductions or pay employees.

Good questions. Clear answers.

A few things you might be wondering.

Have a question about your team’s setup? Talk it through with us.

Is Shift Hub SOC 2 or ISO 27001 certified?

We do not claim SOC 2 or ISO 27001 certification. Tell us about any required certifications or assurance process during the fit review so we can assess whether the current service is suitable.

Are demo requests sent to an AI model?

No. Demo requests are stored in the owner’s inquiry inbox. They are not sent to an AI model for lead scoring or added to the operational assistant’s context. The inquiry privacy notice explains the form’s collection and use.

Can we start without sending employee information?

Yes. A walkthrough can use sample people and shifts. The demo form asks for your business contact details, team-size range and location count, and tells you to leave out employee names and payroll records.

Start with a conversation

Talk through the setup your team needs.

Bring your scheduling challenges. We’ll show you how Shift Hub handles them, then work through whether it’s a fit.

Request a demo

No payment details. No commitment.