People and policy
Build your directory, reporting hierarchy, designations, roles, holidays, and leave policies in one governed workspace.
About HourOps
One operational system for people, work, and billing.
HourOps is a secure B2B workforce operations platform that connects employee administration, projects, timesheets, leave, approvals, reporting, invoice-ready work, and isolated vendor workspaces.
What HourOps does
A connected operating model—not another disconnected HR tool
HourOps follows work from the people doing it to the managers approving it and the organizations paying for it. Permissions and workspace isolation apply throughout that journey.
Work and time
Plan projects and tasks, assign responsibility, capture daily hours, and move submitted work through structured approvals.
Operations and billing
Turn approved work into invoice-ready requests, maintain a clear source of truth, and track subscription invoices separately.
Secure collaboration
Operate primary and sub-account workspaces with row-level tenant isolation while sharing selected projects without exposing private operational data.
Workspace setup
From self-signup to a working organization
The setup sequence keeps organizational structure, policy, security, and people aligned before operational records begin.
1
Create the workspace
An organization owner can register through self-signup. HourOps verifies the email, protects the form with Cloudflare Turnstile, records acceptance of the Terms and Privacy Policy, and creates the initial workspace.
2
Define designations
Create the job titles used by your organization—such as Engineer, Project Manager, HR Manager, or Finance Lead—so employee profiles describe real responsibilities.
3
Configure holidays and leave
Add the organization holiday calendar and reusable company leave types. Set ordinary annual allocations once, synchronize them to employees, and grant audited special leave only when an individual needs it.
4
Build roles and permissions
Use the protected default roles or create custom roles. Permissions determine which pages, records, actions, and AI workflows each person can access.
5
Add users
Create a user individually, invite them by email, or import a validated spreadsheet in bulk. Assign the person’s designation, manager, role group, and account before they begin work.
6
Create projects and tasks
Define project dates and estimated hours, assign eligible project managers, then create tasks and assign them to the people responsible for delivery.
Free and paid access
Begin without payment, upgrade when the model fits
The Free plan is an intentional starting point, not an automatically renewing trial.
Free workspace
No credit card is required. The Free plan supports up to 3 active users, 3 projects, and 15 tasks per project. It does not automatically convert into a paid subscription; an administrator must actively select and confirm a paid plan.
Compare plan capabilitiesSecure paid subscriptions
Paddle is HourOps' Merchant of Record. Paddle presents checkout, processes supported payment methods, and handles applicable transaction taxes. HourOps never stores card details. Paid plans are currently billed monthly, with prorated seat increases and scheduled seat reductions.
Understand paymentsDaily operations
Structured workflows with accountable approvals
Each operational area uses the same identity, role, hierarchy, workspace, and audit foundations.
Timesheets
Employees record time against assigned project tasks. Hours can be split across tasks—for example, six hours on implementation and two on testing. Submitted entries move to a manager or authorized workspace administrator for approval or rejection, with recall and history supporting corrections.
Leave management
Employees request leave against available balances. Managers can approve through multiple levels of the reporting hierarchy, while workspace administrators can act organization-wide. Special grants support compensatory, maternity, paternity, or exceptional leave without changing the company default for everyone.
AI-assisted operations
The AI Assistant turns natural language into a controlled request. It can help view, apply, approve, create, edit, and assign supported records only when the user already holds the corresponding permission. Administrative configuration, subscription actions, and destructive operations remain blocked.
Reports and Work & Billing
Operational reports summarize standard activity, hours, leave, and project performance. Work & Billing converts approved sub-account timesheets into invoice-ready requests, supports approval, rejection, and correction, and keeps one traceable source of truth.
Permissions
What access is required before each process
The names below match the permissions administrators select while building roles. Having access to a page never bypasses server-side validation.
ProcessRequired permissionHow authority is applied
View or change organization detailsView Organization / Edit OrganizationEdit Organization identifies a workspace administrator and unlocks organization-wide operational administration.
Create and maintain usersView Users, Create User, Edit User, Delete UserEach user-directory operation keeps its own permission; Edit Organization does not replace user-management permissions.
Create and maintain rolesView Roles, Create Roles, Edit Roles, Delete RolesRole changes are separate from general organization administration.
Create designations and policiesEdit OrganizationRequired for designations, organization holidays, and creating or editing company leave types.
Assign or grant employee leaveAssign Company LeavesSynchronizes standard allocations and grants audited special leave without resetting leave already used.
Request and approve leaveApply Leaves / Approve LeavesManagers approve within their reporting hierarchy; Edit Organization provides workspace-wide approval authority.
Submit and approve timesheetsSubmit Timesheets / Approve TimesheetsManagers approve within their hierarchy; Edit Organization provides workspace-wide approval authority.
Create, edit, and assign projectsCreate Project / Edit Project / Assign ProjectProject assignees must be eligible to create or edit project tasks. Workspace administrators can manage projects across the active workspace.
Create, edit, and assign tasksCreate Project Task / Edit Project Task / Assign Project TaskTask assignment follows reporting and workspace authority. Destructive deletion remains separately controlled.
Use the AI AssistantUse AI Assistant plus the relevant action permissionAI access alone does not grant an operational action. The assistant checks the user’s action permission, hierarchy, workspace, and tenant boundary.
Manage sub-accountsView, Create, Edit, or Delete Sub-accountsThe exact permission depends on the requested operation. Parent administrators switch into a sub-account before managing its local data.
View subscriptions and invoicesEdit OrganizationAvailable to eligible primary-account administrators. Subscription controls are hidden from sub-accounts.
For the full permission reference, see Documentation.
Account architecture
Primary organizations, sub-accounts, and shared projects
Complex organizations can collaborate without collapsing separate teams into one unrestricted database view.
Primary account
Owns the customer subscription and can create eligible sub-accounts. Its administrators manage primary policies, users, projects, billing, and cross-workspace coordination according to their permissions.
Sub-accounts
Provide isolated workspaces for vendors, contractors, subsidiaries, or business units. Parent administrators switch workspace before acting. Sub-account administrators cannot access subscription controls or delete their own organization.
Project sharing
A project can be shared between organizations while each participating workspace keeps its users, task assignments, timesheets, and operational data isolated. Sharing creates collaboration—not unrestricted tenant access.
Billing records
Subscriptions and operational invoices are clearly separated
HourOps keeps commercial subscription billing distinct from invoices created from approved workforce activity.
Subscription invoices
Eligible primary-account administrators can view the current plan, subscription status, HourOps subscription records, and related invoices. Paddle separately supplies payment or tax documentation as Merchant of Record.
Work-to-invoice records
Approved sub-account work can become an invoice-ready request in a few clicks. Parent and sub-account reviewers can approve, reject, correct, and trace the request while preserving the underlying timesheets as the source of truth.
Explore timesheet invoicingAccount lifecycle
Control renewal, deactivate safely, or permanently delete
These are separate actions with different outcomes. HourOps places sensitive lifecycle operations behind explicit permissions and confirmation.
Cancel subscription
Cancellation stops the next renewal. It does not retroactively cancel the current billing period or automatically create a refund. Current access follows the terms displayed when cancellation is confirmed.
Cancellation detailsDeactivate organization
Deactivation prevents ordinary workspace use while retaining recoverable organization data. It is a protected primary-account administration action and is different from permanent deletion.
Delete organization
Permanent deletion is irreversible. After explicit confirmation and one-time-password verification, organization access is disabled immediately and the protected background deletion begins. An owner can request a structured, LLM-friendly data export before deletion. HourOps prepares it as a manually started background job and emails the protected download when ready without sending the data to an LLM.
Clear deletion policy
Read the Data Policy Operational workspace data is deleted permanently. Limited payment, subscription, dispute, and deletion records may be retained for up to 180 days for compliance and security.
Built around least privilege and a reliable source of truth
HourOps checks authorization in the interface and again on the server. Active-workspace context, reporting hierarchy, role permissions, audit history, and PostgreSQL row-level security work together to keep operational actions within their intended boundary.