docketbeta
Create your account

Inviting your team

Add teammates, choose their role, and understand what a new user means for your bill.

Your workspace lives at your own subdomain — your-agency.godocket.app. Everyone on your team signs in there with their own account.

Add a teammate

Team members are created by an Admin under Admin → Users → New user:

  1. Enter their name, email and username.
  2. Pick their role — it decides what they can see and do, especially whether they see financial data. See User roles & permissions.
  3. Pick their service (expertise) — the rate that represents their work (used e.g. when time is imported from Jira). Required for every new user.
  4. Set their working hours — the weekly target their booked time is measured against (see Working hours).
  5. Set an initial password and save.

The new teammate receives a welcome email with a personal link to set their own password. The link is valid for a few hours — if it expires, the normal "forgot password" flow on the login page does the same job.

What a new user costs

docket is billed per seat, priced by role: every active (non-archived) user counts as one seat, and the role decides the seat's price — Timetracker seats are the cheapest, Project Manager and Admin seats the most expensive. Current prices are on the pricing page.

The seat count syncs to your subscription automatically — adding a user (or changing a role) updates it, archiving a user frees the seat; you never adjust the subscription by hand. Your plan and invoices live under Admin → Billing.

So: give everyone who works with docket their own login with the smallest role that fits — and archive people who leave rather than keeping spare accounts around "just in case".

Removing access

When someone leaves, archive them (Admin → Users → edit). Archiving:

  • ends their access immediately — active web sessions and API tokens are revoked on the spot, and archived users can't sign in again,
  • removes them from team lists and pickers,
  • frees up their seat on your bill,
  • keeps their history intact: booked time, comments and authored tickets stay attributed to them.

Un-archiving restores the account — same history, and they can sign in again (via "forgot password" if they've been away a while).