Use case

Team management

Seven built-in roles, fine-grained permissions, invite-based onboarding.

The problem

Sharing logins is a security nightmare. Most tools force binary admin/worker; real teams need a spectrum.

How it works

  1. Step 01

    Add a worker

    Name + email + role; (optional) department / job title.

  2. Step 02

    Send the invite

    Per-worker link, copyable + revocable.

  3. Step 03

    Track activity

    Per-worker activity feed + status tracking.

What it includes

  • Seven roles

    owner / admin / manager / foreman / worker / contractor / subcontractor.

  • Per-feature permissions

    Each role mapped to a permission matrix.

  • Invite links

    Copy, share via WhatsApp, revoke.

Why teams use it

  • Right-size access without sharing logins.
  • Onboard in minutes.
  • Audit every worker's contribution.

Modules involved

Frequently asked

Can I create custom roles?

Custom roles ship later. Built-ins cover most.

Do contractors count toward plan limits?

Yes — active members count, archived don't.

Can I bulk-import a team?

Yes — CSV via the migration center.

Are roles enforced server-side?

Yes — action layer + RLS.

Can a worker be in two orgs?

Yes — multi-org switcher.

What about temporary access?

Invite links can be revoked; archive removes access immediately.

See it in your account

Sign up free; activate the right modules; start in minutes.