Operations
Team management with role-aware permissions
One team roster, fine-grained roles, and per-feature access controls. Owners onboard workers in two clicks.
The problem
Most tools force every login into 'admin' or 'worker'. Real teams need foreman, manager, subcontractor, contractor — and each needs the right slice of access.
How it works
- Step 01
Add a team member
Name + email + role + (optional) department / job title.
- Step 02
Send the invite link
Invite walks the worker through password setup.
- Step 03
Track activity
Roles control what each member can see and do — every action is logged.
What's included
Seven built-in roles
owner, admin, manager, foreman, worker, contractor, subcontractor.
Per-feature permissions
Each role maps to a permission matrix — what they can create, edit, view, archive.
Onboarding invite links
Per-worker links, copy/share/revoke, expirable, audit-logged.
Departments + job titles
Organize workers without inventing custom roles.
Status tracking
Invited / active / inactive; archive without losing history.
Activity per worker
Every team member has their own activity feed.
Why teams choose this
- Right-size access without sharing logins.
- Onboard new workers in minutes with an invite link.
- Track contributions per worker with activity logs.
- Keep payroll-relevant info (department, title) in one place.
What it looks like
Screenshot
Team list
Screenshot
Invite link panel
Screenshot
Per-worker activity
Use cases
Small crew
Owner + 3 workers, all on the mobile app.
Multi-site team
Manager per location, foremen on each crew, central admin.
Sub-contractor network
Subs get a limited-access role so they see their jobs without the full client list.
Works well with
Frequently asked
Can I create custom roles?
Custom roles ship later. Today you have seven built-ins — most teams find one that fits without invention.
Do contractors count toward my plan?
Yes — every active member counts. Archived members don't.
Can I bulk-import a team?
Yes — paste a CSV into the migration center. Each row creates a team_member + (optional) invite.
What happens when I archive a worker?
Their history stays queryable, they can't sign in, and they drop from the active list.
Are roles enforced server-side?
Yes — every action is gated at the action layer and at the database via RLS.
Can a worker be in two orgs?
Yes — multi-org membership is supported via the org switcher.
Try Team management with role-aware permissions
Free for small teams. Activate it on your account in one click.