Core Concepts
The key building blocks of Optserv: Company, Workspaces, People, Roles, and Plans.
Before you configure Optserv, it helps to understand the five building blocks that everything else is built on.
Company
Your company is the top-level container. All people, settings, roles, workspaces, and data belong to a single company. Access is strictly company-scoped — one company can never see another's data.
Every Optserv user belongs to exactly one company at a time.
Workspaces
Workspaces are logical modules within your company. Each workspace has its own routes, features, and access rules.
| Workspace | Route | Purpose | Enabled by default? |
|---|---|---|---|
| HR | /hr | People operations — attendance, leave, overtime, recruitment | Yes |
| Account Sharing | /accounts | Shared credential management | No — requires account_sharing_enabled |
| School (OptClass) | /school | Education and kiosk-style operations | No — requires school_accessible claim |
Start with HR. Add workspaces when your operational needs require them.
People
People are the employees and teammates in your company. Each person has:
- A role that determines their access level
- An optional department for organizational structure
- A status (active, inactive, offboarded)
When someone is offboarded, their access is removed across all workspaces — not just HR.
Roles
Roles control what someone can see and do in Optserv. There are four staff roles:
| Role | Scope |
|---|---|
| Admin | Full company access — settings, billing, all workspaces |
| HR | People operations across the company |
| Manager | Visibility and approvals for their department |
| Employee | Self-service — personal info, requests, own data only |
Students (OptClass) are outside the staff role hierarchy entirely. They access a separate kiosk-style interface and are blocked from the staff web application.
Principle of least privilege: assign the smallest role that lets someone do their job. Promote when needed, not by default.
Plans
Your plan determines which features you can access and the limits on key resources.
| Limit | Community (Free) | Business with Access |
|---|---|---|
| Employees / users | 15 | Subscription seats (up to 1,000 by default) |
| Published job postings | 3 | Unlimited |
| Applicants per job | 25 | Unlimited |
| Storage | 2 GB | 200 GB |
| School — Students | 25 | Unlimited |
| School — Teachers | 15 | Unlimited |
See Pricing: Free vs Paid for the full breakdown.
How they connect
Company
├── Workspaces (HR, Accounts, School)
│ └── Features (attendance, leave, shared credentials, sessions...)
├── People
│ ├── Role → controls access within workspaces
│ └── Department → controls approval routing and visibility scope
└── Plan → controls feature limits and seat counts
When you invite someone, you set their role and department. Those two values determine everything they can see and do.