HR & People
Employee records, organization, employment history, self-service and protected HR documents.
Overview and core concepts
Employee records, organization, employment history, self-service and protected HR documents.
An Employee is an employer-owned business record, not a login account. An optional User link is approved for one membership and employment episode.
Employment and assignment end dates are exclusive. Dates remain date-only; company timezone fixes UTC access boundaries. Rehire creates a new period and keeps the employee reference.
Private and restricted fields are excluded from directory and manager projections. Only released CLEAN document versions are visible to their linked employee.
Confidential compensation records preserve their effective dates and history. Authorized HR staff can publish a future revision without replacing the current record.
Before you start & permissions
Select the right company and confirm that this app is active.
Every data operation is explicit. Staff operations require an approved HR appointment plus the operation grant. Self and direct-team views derive their employee identity on the server; restricted actions require fresh MFA.
Understanding permissionsGetting started & common workflows
- Ask an authorized CedraStack Owner/Admin to activate or trial HR & People, approve an external or employee-bound HR custodian and grant explicit operations. Enable MFA for protected staff access.
- Review the employer retention policy in HR Settings. Create an employee; add employment before linking a user or creating an assignment. Organization structures are optional.
- Use Employee 360 tabs for private contacts, emergency contacts/dependents, Contracts, Documents and permitted custom fields. Corrections retain history.
- Approve an Employee/User link with a fresh MFA code, then grant only the intended self-service/team operations through Admin access setup. A user link does not grant HR staff permissions.
- Upload a PDF, PNG or JPEG no larger than 5 MiB. Wait for CLEAN before download or sharing. Pending, failed or infected versions remain blocked. Replacement creates a new version and scan.
- Use the Compensation tab on the employee record to draft and publish effective-dated compensation records. Publishing requires fresh MFA. Employees can see only records explicitly shared with them.
- Use explicit HR exports for the permitted category. Existing company exports exclude HR by default. Restricted exports/downloads require fresh action-scoped MFA.
Worked example
Fictional Cedar Studio creates an employee without a login. It records an employment period, then optionally a department and manager. A custodian explicitly links a current company member to that employee and employment period. A clean scanned document is shared with the employee; removing the link immediately removes self-service access.
Related modules
Shared records and explicit handoffs keep work connected. Each module still requires its own access and permissions.
Troubleshooting
- No HR records? Check company entitlement, explicit grants, current staff appointment, current membership and MFA. Owners receive no sensitive HR data by default.
- No My HR? Review the exact Employee/User link and its employment period. Removal, rejoin or rehire does not revive a prior membership/employment link.
- File unavailable? Check scan status and current subject/classification permissions. A CLEAN verdict never bypasses authorization.
- Cannot save an assignment? Check date overlaps, manager cycles, current manager employment, Position occupancy and stale record versions.
Current platform notes
- HR & People can run on its own. Other Business apps are optional.
- Raw government identifiers and bank details are not captured. Employer-approved retention and processing policies are required before using real personal data. HR exports currently include structured data; binary documents use individually authorized downloads.
- Company Owner status alone does not grant HR data. Sensitive actions need fresh MFA and current appointment, membership and operation permissions.
Setup, privacy and Employee 360
Ask an authorized CedraStack Owner/Admin to activate or trial HR Beta, approve an external or employee-bound HR custodian and grant explicit operations. Enable MFA for protected staff access.
Review the employer retention policy in HR Settings. Create an employee; add employment before linking a user or creating an assignment. Organization structures are optional.
Use Employee 360 tabs for private contacts, emergency contacts/dependents, Contracts, Documents and permitted custom fields. Corrections retain history.
Approve an Employee/User link with a fresh MFA code, then grant only the intended self-service/team operations through Admin access setup. A user link does not grant HR staff permissions.
Upload a PDF, PNG or JPEG no larger than 5 MiB. Wait for CLEAN before download or sharing. Pending, failed or infected versions remain blocked. Replacement creates a new version and scan.
Use explicit HR exports for the permitted category. Existing company exports exclude HR by default. Restricted exports/downloads require fresh action-scoped MFA.
Access and current limits
Use Performance and talent for reviews, goals, skills, certifications and training. Attendance is separate from Projects Time and creates neither billable time nor payable time. HR can run on its own.
Raw government identifiers and bank details are not captured. Employer-approved retention and processing policies are required before using real personal data. HR exports currently include structured data; binary documents use individually authorized downloads.
Company Owner status alone does not grant HR data. Sensitive actions need fresh MFA and current appointment, membership and operation permissions.
Schedules, holidays and leave
In HR → Schedules & policies, explicitly configure every weekday as rest, flexible duration or fixed intervals. Times use company-local minutes after midnight; an end above 1440 crosses midnight. No working week, statutory entitlement or grace period is assumed.
Create a dated holiday calendar and assign a schedule/calendar to the company, a Location or an Employee. Employee overrides take precedence over Location, then company. Versions and submitted calculations are retained. Nonexistent DST times reject; repeated times need an explicit earlier/later choice.
Create a Leave Type with one permanent unit: whole minutes or thousandths of a day (1000 = 1 day, 500 = half a day). Create an effective-dated policy with employer-approved eligibility, accrual, cap, negative limit, carry and expiry rules. Once a policy has an account, changing the anchor/frequency needs a new policy/account rather than moving an old cursor.
Open a Leave account for the exact employment period; post an explained opening/entitlement/adjustment. Balances come from immutable entries and grant lots, not a mutable employee field. Earlier-expiring valid grants are consumed first.
My leave can preview/save a draft, review its retained schedule and submit. Submission reserves balance. A currently authorized direct manager or HR approver consumes the hold and posts one usage entry; no second debit occurs on the leave date. A different approver is required. If no eligible manager is available, HR handles the request.
Cancel drafts/pending requests to release holds. Authorized HR cancels approved requests with an immutable reversal; expired entitlement stays expired. Reasons and supporting documents are not shown to a manager merely because they approve leave. Required documents reuse authorized PRIVATE_EMPLOYEE files and must pass scanning.
Attendance, corrections and safe exports
Configure explicit arrival/departure grace minutes and optionally enable web clocking. My attendance records the authenticated Employee at the server UTC instant. There can be one open interval. Checkout names that interval; retries do not create duplicate clock events. An overnight shift retains its scheduled work date.
Authorized HR can enter a bounded interval for an Employee without a user account. Raw events remain immutable. A correction is a separate request; a different authorized current manager/HR reviewer approves or rejects it. Approved amendments update the effective summary while retaining the original interval.
No event means Unrecorded by default. Absence inference is an explicit employer choice for closed scheduled days. Approved leave is an explanatory link, never an invented clock event. Worked holidays remain recorded. Overtime is Calculated, Approved or Rejected for the current day version; no wage multiplier or payment is created.
My Team reads only currently authorized direct reports. Membership, link, reporting changes, termination, MFA and permission removal are checked again on reads/decisions. HR presence is not published in the general employee directory.
Use the dedicated private Leave or Attendance export form with an explicit date range (maximum 366 days), optional selected Employee and EXPORT confirmation. Archive preparation runs in the background. The requesting company Owner needs current HR access, an HR appointment, topic read and private export grants; all checks repeat during processing and download. Ordinary company exports exclude these datasets.
Initial attendance admission is reviewed for up to 100 currently employed HR Employees across CedraStack companies. New clock/entry admission fails closed if database size metadata is unavailable or reaches 8 GB. Existing checkout and authorized history/corrections remain separate. Ask for a capacity review before expansion; no automatic deletion or universal retention rule is applied.