Skip to main content
GullyHR

HR technology and automation · Video conferencing solution providers

Employee and Manager Self-Service for Video conferencing solution providers

Employee and manager self-service is the GullyHR module that gives each employee their own profile, leave balance, attendance, payslips, letters and current policies, and gives each manager a view of their team, the approvals sitting with them and the queries raised through the helpdesk. Requests are raised and decided where they belong instead of passing through HR on the way.

An employee using a laptop while a manager offers guidance from beside the desk.

The operating context

Give each user the right view and request route

Video conferencing solution providers connect room design, installation and user support. HR readiness should cover the relevant AV and network skills and clarify who owns end-user training and post-installation issues.

AV solution designersInstallation engineersNetwork coordinatorsSupport technicians
A developer discussing career progression with an engineering manager and HR partner

The decision to work through

Configure employee and manager access to records, requests and approvals according to the reporting structure. Workforce to consider: AV solution designers, Installation engineers, Network coordinators.

Records and configuration to test

User-role matrix, request forms and self-service tests. Plan evidence collection around customer installation windows and acceptance dates.

An exception to test

Test a reporting-manager change and confirm that the former manager loses access to the employee's restricted information.

Which parts of your business should the scope cover?

The right workforce and approval structure depends on the operations you run. Confirm which of these apply, and whether they share one HR process.

  • Corporate boardrooms and meeting rooms
  • Schools, colleges and coaching institutes with hybrid classrooms
  • Hospitals using video for case discussions and training
  • Government and public sector conference halls
  • Hotels and convention venues
  • Law, audit and consulting firms with client calls

When to consider this service

  • Every leave application arrives as a message to HR, who then check the balance and forward it to a manager anyway.
  • An employee asks for last month's payslip because there is nowhere they can go and find it.
  • A manager has no single view of who on their team is out today or what is sitting unapproved with them.
  • Questions about what the policy says come to HR instead of to the policy.

Businesses this service is designed for

  • Companies where every routine request, leave, payslip, document or policy question, currently arrives as a message to HR.
  • Growing businesses where one HR person supports enough people that handling each request by hand no longer fits in the week.
  • Multi-site businesses whose managers cannot see their team's attendance or leave without calling head office.
  • Companies already running GullyHR for employee records, attendance or payroll inputs who now want people to reach that data themselves.

What the system needs to support

GullyHR configures what employees and managers can see and do for themselves, and builds the request and approval workflow behind it, reading the employee, attendance, leave, payroll and document records the platform already holds. You make the judgement calls: which fields an employee may change directly and which need approval, what a manager may see of their team, which requests still belong with HR, and where the approval route runs. We configure the employee and manager views, the approval routing, the helpdesk categories and the access rules that keep each person inside their own record or their own team, then train all three groups. It is delivered as a configuration and rollout stage within a GullyHR software engagement, alongside the modules it draws on.

An employee can see their own record without asking anyone.

Personal, employment and statutory details are visible to the person they describe, with a request route for the fields that should not change without approval, so corrections start with the employee rather than a form.

Leave is applied for by the person taking it.

An employee sees their attendance, entitlement and balance, applies directly, and the request routes to their reporting manager, which removes HR from the middle of a transaction it was never really deciding.

Payslips and letters are collected, not requested.

Employees reach their own payslips, appointment and other letters and acknowledged policies from the document centre, so HR stops re-sending documents it has already issued once.

The current policy is readable by the people it applies to.

Employees read the version-controlled policy that applies to their role, department or location, rather than asking HR what it says and getting one person's recollection of it.

A request has a status instead of a silence.

Leave, document and change requests move through a tracked workflow, so the person who raised one can see where it is and the person who must act on it can see it is waiting.

A manager can see their own team without asking head office.

Reporting structure, attendance and leave status for the manager's own reporting line, so planning the week does not start with a call to head office. This matters most at a site where HR sits somewhere else entirely.

Pending approvals stop hiding in an inbox.

A manager's dashboard shows what is waiting on them and what their team's week looks like, so an approval is missed by decision rather than by accident.

An employee question becomes a tracked query.

The helpdesk gives employees a route for an HR question, sorted into the categories you configure and routed to whoever should answer it, with a status the employee can check.

Configure, validate and prepare users

Map the approved process to fields, user roles, permissions and workflow rules. Inspect the source data and identify migration, integration and reporting requirements before configuration.

  1. 01

    Access scope review

    We agree what employees and managers can view and action directly, what needs an approval step, and what should still route through HR.

  2. 02

    View configuration

    Employee and manager views are configured against the employee, attendance, leave, payroll and document records already held in the platform.

  3. 03

    Request workflow setup

    Leave, document and change requests are configured with the approval route that matches your reporting structure and any exceptions to it.

  4. 04

    Manager dashboard setup

    Each manager's dashboard is configured to show their own reporting line: team status and the approvals waiting on them, and nothing beyond that.

  5. 05

    Helpdesk configuration

    Query categories and routing are set up around the questions HR actually receives, so a query reaches an owner rather than a shared inbox.

  6. 06

    Roles and permissions

    Access is restricted so an employee reaches only their own record and a manager only their own team, including where somebody manages across departments.

  7. 07

    Communication and training

    Employees and managers are shown the handful of actions they will use, and HR administrators are shown how to configure and monitor them. Adoption depends on this being brief and specific.

  8. 08

    Go-live and review

    Self-service goes live for the agreed group, and after the first cycle we look at what people did not use, what they still asked HR for, and what needs opening up or closing down.

Test migrated records, approvals, exceptions and permission boundaries with representative users. Agree acceptance, user training, support ownership and the handling of remaining issues before go-live.

Agreed configuration and handover

  • Configured employee and manager self-service views inside the GullyHR platform.
  • A configured leave, document and change-request approval workflow matching your reporting structure.
  • A configured manager dashboard scoped to each manager's own reporting line.
  • A configured employee helpdesk with query categories and routing rules.
  • Role-based access rules restricting each person to their own record or their own team.
  • Training sessions for employees, managers and HR administrators.
  • A short reference guide covering the common self-service actions, written for employees rather than administrators.
  • A post go-live review covering usage, gaps and what to open up next.

What your team provides

  • Which fields an employee may change directly and which need approval.
  • What a manager may see about their team, and which requests stay with HR.
  • Your reporting structure and the approver at each level of the route.
  • The helpdesk categories you want and who answers each one.

Share personal records only after the scope, access and handling arrangements are agreed.

Responsibilities and approvals

The client owns employee records and approves policies, spending and employment decisions. GullyHR's assigned responsibilities are documented in the engagement.

Deciding what people can do themselves

GullyHR
Sets out the options, explains what each one means for HR's workload and for control, and configures the agreed scope.
Your team
Decides which actions employees and managers complete directly and which still require HR or an approval.

Setting the approval route

GullyHR
Configures the routing to match the reporting structure and the exceptions you name.
Your team
Confirms the reporting structure and who approves where the normal manager is unavailable or is the subject of the request.

Configuring the helpdesk

GullyHR
Sets up categories, routing and status handling.
Your team
Confirms the categories that match the queries actually received, and names an owner for each.

Getting people to use it

GullyHR
Runs training for employees, managers and HR administrators on the actions each will perform.
Your team
Makes people available for training and tells the organisation that this is now the route, which is what decides whether adoption happens.

Running it after go-live

GullyHR
Remains available for configuration changes as roles, routes or categories change.
Your team
Owns day-to-day monitoring of requests, approvals and helpdesk queries, and answers what the system routes to it.

How we agree that the work is complete

Review these outputs with your process owner and agree the evidence required for sign-off.

  • Employee and manager views are configured, and a test employee sees only their own record.
  • A test manager sees only their own reporting line, confirmed against your reporting structure.
  • Leave, document and change requests route to the approvers you named, confirmed with test requests.
  • Helpdesk categories exist with a named owner each, and a test query reaches the right person.
  • Employees, managers and HR administrators have each been trained and have a short reference guide.

Data, configuration and adoption

Self-service reads the same employee, attendance, leave, payroll and document records held elsewhere in the platform, so the balance an employee sees on their own screen is the balance HR sees, not a copy that drifted. Approval routing follows the reporting structure configured in core employee management, which is why a request reaches the right manager without HR forwarding it, and why a stale reporting line shows up here first. Access is restricted by role, so opening the system up to everyone does not open the data up to everyone: an employee reaches their own record and a manager their own line. Employees and managers use it on whatever device they log in from, which is the part that decides whether a shop-floor or field employee ever uses it at all. What self-service does not change is who holds authority. It changes who raises and who tracks a request, not who is entitled to approve it.

Limit access to the records needed for the agreed work. Confirm authorised users, secure sharing, retention and return or deletion arrangements before exchanging personal information.

Read the full employee and manager Self-Service service guide →

Agree the engagement before work starts.

Demonstration and configuration

A walkthrough of the employee and manager views, followed by configuration to the actions, routes and access you decide on.

Phased rollout

Self-service can start with one action, such as leave, before opening up documents, profile changes and the helpdesk, which is gentler on both employees and HR.

Ongoing support

Continued support as roles, approval routes or helpdesk categories change after go-live.

Scope and exclusions

  • Confirm product fit, licensing and the implementation scope before committing. Custom development, third-party integrations and GullySystem services are separately agreed; they are not automatically included.
  • Your employee records are incomplete or inconsistent and need cleaning before anyone is given access.
  • You want employees able to change any field, including pay or bank details, without an approval step.
  • You want a helpdesk that investigates grievances, rather than routing routine queries to HR.
  • You want self-service on its own, without the modules it reads from.
Confidentiality, specialist review and accountability

Limit access to the records needed for the agreed work. Confirm authorised users, secure sharing, retention and return or deletion arrangements before exchanging personal information.

Applicability depends on locations, workforce arrangements and the issue under review. Confirm applicable requirements with your qualified adviser before adopting policies or employment actions; this service is not a legal certification.

Employment-law opinions, statutory filings, professional or clinical standards and safety-critical technical decisions require the appropriate qualified professional; include those dependencies in the scope.

Questions before you decide

For video conferencing solution providers, identify who owns these records: user-role matrix, request forms and self-service tests. Start with an anonymised example and the decision you need to make; agree the sample and access before sharing personal data.

Discuss your HR system

Tell us the teams and locations involved, what is happening today and what you want this work to resolve.

Start with your business need

What does your HR team need to solve?

Tell us your industry, team size and the issue you want to address. Bring one example of where work gets delayed or ownership is unclear, and the deadline or decision you are working towards.

  • A free first conversation with an HR practitioner
  • A clear scope and fee before any paid work
  • A practical next step for your business

Let’s start with your business

Share your contact details and the HR challenge on your mind. We’ll help you find the right starting point.

Include your country code, for example +44 or +1. Indian numbers can be 10 digits.

Your details stay private. Privacy policy