Hive · Team workspace guide

Joining and growing your WorkHive hive (your team's private workspace)

By WorkHive Editorial Team · Published 17 May 2026 · Updated 17 May 2026 · 7 min read

Short answer: A WorkHive hive is your plant's isolated workspace containing assets, logbook, PM schedules, people, and history. Workers can use WorkHive in solo mode (private to them) or join a plant hive (supervisor-approved). Each hive has 4 role levels (field, supervisor, engineer, plant manager) with role-based access control. Data isolation is enforced at the database row level; nothing leaks between hives. Multi-site operations use hive groups for corporate roll-up while keeping each plant autonomous day-to-day.

Who this is for

New workers signing up to WorkHive
Plant managers setting up a hive
Supervisors approving new members
Engineers joining multiple sites
Contractors with scoped access needs
OFW-track workers in solo mode
New graduates building portfolios

What a hive is, in concrete terms

The hive is WorkHive's team workspace: a private space for one plant's team. One plant equals one hive. Inside the hive:

People: every worker who has joined this hive with their role and skill matrix
Assets: the canonical asset register in Asset Hub
History: all logbook entries, PM completions, fault notifications, parts consumption
Schedules: PM plans, shift handovers, day planner blocks
Knowledge: AI Assistant context trained on this hive's data

Workers in Hive A cannot see Hive B's data. Period. No path through the UI, no path through the API, no path through the AI assistant. This is the foundation that lets a Cabuyao chocolate factory and a Cebu food plant both use the same WorkHive platform without ever leaking data to each other.

Solo mode: WorkHive without a plant

Many workers do not have a plant hive yet. They might be:

A freelance maintenance engineer between contracts
An OFW-track new graduate building a portfolio for the Saudi or UAE market
A contractor whose client has not adopted WorkHive yet
A student learning industrial maintenance during practicum
A worker whose plant is still on paper and they want to start digital personally

Solo mode is for them. Sign up with email, get the full WorkHive toolset (Logbook, Engineering Design, Skill Matrix, AI Assistant, Day Planner) scoped to a personal hive of one. Solo data stays private; nobody else sees it. When the worker later joins a plant hive, they choose what solo history to import (skill matrix evidence usually comes with them; logbook entries from a previous employer usually stay private).

This is one of the under-told values of WorkHive: it works as a personal professional toolkit, not only as a plant tool.

How to join an existing plant hive

Three steps:

Sign in or create an account. Email plus password; takes about 30 seconds.
Find the hive. Either enter the hive code your supervisor gave you, or search the directory for your plant by name.
Request to join. Pick your role (field, supervisor, engineer). Supervisor sees the request and approves within minutes.

After approval, the worker gets immediate access to the hive's tools. Existing logbook entries become searchable; PM assignments start appearing in their queue.

The 4 role levels and what each can do

Role	Can do	Cannot do
Field	Log entries, view assets, complete assigned PMs, use AI assistant, voice journal	Approve PMs, assign work, edit skill matrix, see financial views
Supervisor	Everything in Field plus assign work, approve PMs, edit skill matrix, draft handovers, view team analytics	Edit engineering calculations, change integration config, see AI Quality dashboard
Engineer	Everything in Supervisor plus engineering design tool, deep analytics, integration setup, asset register edits	Approve plant-level budgets, change hive roles
Plant Manager	Everything in Engineer plus AI Quality dashboard, full audit log, financial views, hive role changes, founder console access	Nothing within their hive; everything is available

Roles are additive (Plant Manager can do everything a Field worker can). Workers do not see tools they cannot act on; the nav adapts based on role.

The tool this guide is about

WorkHive Hive is your plant's workspace

The Hive dashboard is the supervisor's home for the plant team: who is in the hive, who is requesting to join, current PM compliance, open issues, and adoption score. Set up your hive once and every other WorkHive tool inherits the membership and roles. Free at the worker tier; multi-site hive groups and corporate roll-up unlock at Stage 4.

Open the Hive Dashboard

No hive yet? Join WorkHive first (free, takes 30 seconds).

Data isolation between hives

Multi-tenancy in industrial software is hard because the consequences of leakage are severe. A competitor seeing your fault history, a supplier seeing your consumption forecast, a contractor seeing your cost data: any of these is grounds for losing the platform's trust.

WorkHive enforces isolation at three layers:

Automatic per-hive data isolation: every query the app makes is scoped to your hive's ID on the database server itself, so one hive can never read another's records. There is no "view all" backdoor.
API token scope: integration tokens are bound to a single hive. A leaked token for Hive A cannot retrieve Hive B's data.
AI assistant context: the AI's vector store and retrieval index are partitioned per hive. The AI literally cannot answer a question with another hive's data because it cannot read it.

Cross-hive access exists but only via explicit, scoped, named permissions: a contractor whose work spans multiple plants, a supplier on consignment stock across a network. Default is total isolation.

Multi-site operations and hive groups

Filipino conglomerates often run 3 to 20 plants across the country. The pattern that works:

Each plant is its own hive. Day-to-day operations stay autonomous; each plant's supervisor manages their own membership and PM schedule.
A hive group ties them together. The corporate maintenance director gets a roll-up dashboard showing PM compliance, MTBF, MTTR, and OEE across all child hives without seeing operational detail.
Per-plant benchmarking becomes natural. Plant A's PM compliance is 87 percent; Plant B's is 62 percent. The corporate team can see the gap and dispatch help.

The bigger picture: The hive is not just a workspace; it is the trust boundary. Plants adopt WorkHive because the boundary is real and enforced at the database. Workers join hives because their data goes with them when they leave (skill matrix history, work portfolio). Both halves of the trust equation are needed for a free industrial platform to work in the Philippines, where data sensitivity is high and trust in cloud SaaS is still being earned.

Frequently asked questions

What is a WorkHive hive?

A hive is your plant's isolated workspace in WorkHive. Each hive contains its own assets, logbook entries, PM schedules, skill matrix, and people. Workers from one hive cannot see another hive's data without explicit cross-hive permission. The hive is the unit of multi-tenancy: one plant equals one hive (or a group of hives for multi-site operations).

Can I use WorkHive solo, without a plant hive?

Yes. Solo mode lets an individual worker (a freelance maintenance engineer, an OFW-track new graduate building a portfolio, a contractor between gigs) use the full WorkHive toolset (Logbook, Engineering Design, Skill Matrix, AI Assistant, Day Planner) without joining any plant. Solo data stays private to that worker. When the worker joins a hive later, they can choose what solo history to import or keep separate.

How does joining a plant hive work?

Three steps: (1) the worker creates an account or signs in; (2) the worker enters the plant's hive code or search the directory and request to join; (3) the plant's supervisor approves the request. Approval typically takes minutes; the supervisor sees who is requesting and assigns the appropriate role (field, supervisor, engineer). The new joiner gets immediate access to the hive's data and tools.

What roles exist within a hive?

Four primary roles: field (technician or operator with logbook + asset access), supervisor (everything plus PM approval, skill matrix edits, work assignment), engineer (everything plus engineering design, analytics deep-dives, integration config), and plant manager (everything plus AI quality dashboard, full audit log, financial views). Roles control what each worker sees and can do; nobody sees a tool they cannot act on.

How is plant data kept private from other hives?

Data isolation is enforced at the database row level itself. Every query the WorkHive app makes is automatically scoped to the joined hive's data. There is no path through the UI or the API for a worker in Hive A to see Hive B's data. Contractors and suppliers who need cross-hive access get explicit scoped permissions; nothing else crosses the boundary.

What about multi-site operations (a company with several plants)?

Each site is its own hive. The parent company can create a hive group that lets the corporate maintenance director see roll-up KPIs across all child hives without seeing operational detail. Each child hive remains independent for day-to-day operations. This is the pattern for Filipino conglomerates running 3 to 20 plants across the country who want benchmarking without violating per-site autonomy.

Sources

Supabase, Row Level Security documentation. The PostgreSQL feature WorkHive uses to enforce hive isolation at the database layer.
WorkHive platform positioning, "Four Gaps One Hive" with the hive as the per-plant boundary. workhiveph.com
Related WorkHive guides: Digital logbook rollout · Skill matrix

WorkHive Editorial Team

Practical writing for the Philippine plant floor. Email admin@workhiveph.com with corrections or contributions.

← Back to all guides