Keep Employee Information Organised in One HR System
Employee details spread across a joining-form folder, a payroll spreadsheet and someone's memory make a simple question, such as who reports to whom, take longer than it should. Core employee management keeps one employee record, one organisation structure and role-based access, so the same information is used everywhere it is needed.
What is core employee management?
Core employee management is the GullyHR module that holds one employee database covering personal, statutory, salary, reporting and document details, alongside your organisation structure, departments, locations, designations and reporting hierarchy. Access to each field is role-based, so employees, managers and HR administrators see only what their role needs.
When businesses ask us for this
- An employee's phone number, bank account or emergency contact is different in three different files, and nobody knows which is current.
- A new manager takes over a team and has to ask around to find out who actually reports to them.
- HR documents such as offer letters, ID proof and educational certificates are scattered across email attachments and a shared drive.
- A designation or department change happened weeks ago and payroll or reporting still reflects the old one.
- Anyone with access to the employee spreadsheet can see everyone's salary, whether or not that is appropriate for their role.
- A new location or department opens and there is no defined place in the records for it to sit.
- Management asks for a headcount by department and location, and someone has to manually count rows in a spreadsheet.
What the work covers
Core employee management is the base module of the GullyHR platform, the record every other module refers back to. We configure your organisation structure, departments, locations and designations, define the reporting hierarchy, set up the employee record fields you use, and migrate your existing employee data into it. You provide your current employee data, your organisation chart and reporting lines, and the access rules you want applied by role. Delivery runs as configuration, data migration and role-based training as part of a GullyHR software engagement, not a standalone data-entry exercise.
Employee database
One record per employee covering personal details, statutory identifiers, salary structure, reporting line and status, replacing data spread across spreadsheets and files.
Organisation structure
Your company's structure configured in the system, including group or brand structure where more than one entity operates under common ownership.
Departments and locations
Departments and work locations set up to match how your business actually operates, so every employee record sits against the correct one.
Designations and roles
A designation list configured to your grading or title structure, kept consistent across employee records instead of being typed freely each time.
Reporting hierarchy
Each employee's reporting manager configured in the system, so approvals in attendance, leave and other modules follow the actual reporting line.
Employee documents
A place to hold each employee's documents, such as identity proof, offer and appointment letters and certificates, against their record rather than in separate folders.
Role-based access
Access to view or edit employee information defined by role, so a manager sees their team's relevant details and an employee sees their own record without exposing everyone else's.
How it runs
Structure mapping
We review your current organisation chart, departments, locations and designations, and confirm the structure to be configured.
Field and access configuration
We agree which employee data fields are captured and who, by role, can view or edit each of them.
Data collection and migration
Existing employee data is collected from your spreadsheets or files in the format we specify, and loaded into the system.
Data verification
Migrated records are checked against your source data, and discrepancies are corrected before go-live.
Reporting hierarchy setup
Each employee's reporting manager is configured, since attendance, leave and other module approvals rely on this line.
Role and permission setup
Business owner, HR administrator, manager and employee roles are defined with the access agreed during configuration.
Training
HR administrators are trained to maintain records and process changes; managers and employees are shown how to view their own or their team's information.
Go-live and review
The module goes live, and after a short period we review whether the structure and access rules are working as intended, adjusting where needed.
What you receive
- A configured employee database matching your organisation structure, departments, locations and designations.
- Migrated employee records, checked against your existing data before go-live.
- A configured reporting hierarchy used by attendance, leave and other module approvals.
- Role-based access rules for business owner, HR administrator, manager and employee users.
- Employee documents attached to individual employee records.
- An HR administrator training session covering record maintenance and change processing.
- Reference documentation for maintaining the employee database going forward.
Who it is for
- SMBs currently holding employee data in spreadsheets, joining-form folders or a mix of both.
- Multi-location or multi-department businesses where organisation structure needs to be consistent and current.
- Companies that have just hired their first HR administrator and need a structured record to work from.
- Businesses preparing for a funding round, audit or inspection where employee records will be reviewed.
- Growing companies adding designations, departments or locations faster than a spreadsheet can be kept accurate.
Why GullyHR.
Because GullyHR also consults on organisation design and role definition, the structure configured in this module is set up to reflect a reporting line and designation set your management has actually agreed, not a generic template you then have to work around. If your organisation structure itself needs review before it is configured, that work is available from the same team.
What changes
- Employee information exists in one place, reducing the number of files a manager or HR administrator has to check.
- Reporting hierarchy in the system matches who actually manages whom, so approvals route correctly in other modules.
- Employee documents are attached to the employee record instead of scattered across email and shared drives.
- Access to salary and personal details is limited by role, rather than open to anyone with the spreadsheet.
- Headcount, department and location counts are available from the system rather than a manual count.
- A new department, location or designation is added once in configuration and is then available wherever it is needed.
Who does what
| Activity | GullyHR | Your team |
|---|---|---|
| Providing employee data | Specifies the required data format and fields. | Supplies current employee records from spreadsheets or existing files. |
| Confirming organisation structure | Configures departments, locations, designations and reporting lines as agreed. | Confirms the structure and reporting lines to be used, including any changes intended alongside implementation. |
| Deciding access rules | Recommends role-based access options and configures the rules agreed. | Decides who, by role, should see or edit salary, personal and document details. |
| Verifying migrated data | Loads and checks data against the source before go-live. | Reviews a sample of migrated records and confirms accuracy. |
| Ongoing record maintenance | Provides training and remains available for configuration changes. | Maintains day-to-day updates, such as new joiners and changes, once trained. |
Where the software fits
Core employee management is the record other GullyHR modules read from and write to: an attendance entry, a leave approval, a payroll input and a performance review all reference the same employee record and reporting line, rather than each module holding its own separate copy of who someone is or who they report to. Access is role-based and configured to your structure, so a manager sees their own team's records and an employee sees their own, without a separate access request each time. The module is designed for use by HR administrators, managers and employees on a computer or a mobile browser. Where you already hold employee data in another system, we specify the export format needed and migrate it in; a live, ongoing integration with a separate system would need to be scoped and confirmed on its own.
Ways to engage us
- Demonstration and scoping
- A walkthrough of the module against your current structure and data, followed by agreed scope for fields, structure and access.
- Configuration and migration
- Structure and access configured, existing data migrated and verified before go-live.
- Ongoing support
- Continued support for structure changes, such as a new location or designation, as your business grows.
Questions we are asked
It holds one employee record per person covering personal, statutory, salary, reporting and document details, alongside your organisation structure, departments, locations, designations and reporting hierarchy, with role-based access to what each user can view or edit.
Yes. It is commonly the first module a small business configures, and it scales to multiple departments and locations by configuring each one and assigning employee records to the correct structure.
Yes. We specify the data format needed, collect your existing employee data from spreadsheets or files, load it into the system and check it against your source records before go-live.
Within GullyHR, this module is the base record other modules such as attendance, payroll input and performance draw on directly. Connecting to a separate external system would be scoped as its own requirement.
Implementation includes structure mapping, configuration, data migration and verification, followed by an HR administrator training session and guidance for managers and employees on viewing their own information.
Access is role-based and configured during setup. Typically HR administrators and specified approvers see salary and personal details, managers see limited team information relevant to their role, and employees see their own record.
Yes. New departments, locations and designations can be configured after go-live as your business changes, and this is normally covered under ongoing support.
It reduces reliance on physical or scattered digital files by holding employee documents against each employee's record, though original signed documents and statutory filings may still need to be retained separately as required by law.
The module is designed for use by HR administrators, managers and employees on a computer or a mobile browser, so viewing basic employee or team information does not require being at a desk.
After a demonstration and a review of your current data and structure, we agree the fields, structure, access rules and migration effort involved, and the proposal sets out scope and delivery before work begins.
Prefer to talk first? +91 80958 58589 · hello@gullyhr.com