← All articles
BLOG

Owners, staff and watchers: who should see which license

· 3 min read

Giving everyone on a team the same access is the simplest way to set up a workspace, and it works fine right up until someone who only needed to see a renewal date discovers they can also change billing, remove a teammate, or delete a license. Roles exist so that trade-off never has to happen.

The idea isn’t to lock people out of things. It’s to match what someone can do to what they actually need to do, so the person renewing a license and the person paying for the account aren’t forced into the same permissions by default.

The roles

  • Owners handle billing, team membership and workspace settings — the decisions that affect the whole account.
  • Staff do the day-to-day work of keeping licenses renewed: adding records, uploading documents, confirming dates.
  • Watchers and supervisors can see status without owning the renewal themselves, useful for a manager who needs visibility but isn’t the one doing the paperwork.

Why a separate watcher role is useful

A supervisor who needs to know the moment something slips into “overdue” doesn’t necessarily need the ability to edit the record, upload a new document, or reassign who owns it. Watching status without the ability to change it keeps oversight separate from execution — the person checking the work isn’t the same permission level as the person doing it.

Nothing is left unassigned

A license with no one named on it defaults to the owners, so there’s never a record that genuinely belongs to nobody — even if it’s not where you meant to leave it long-term. That default matters most right after a license is imported in bulk or added quickly without stopping to assign it properly.

Sensitive changes ask twice

Changing team membership, billing or security settings — and deleting a license — all require a fresh two-factor code, even in a session that’s already signed in. It’s a small amount of deliberate friction on exactly the actions worth slowing down, the ones that are hard to undo or easy to regret if done by accident.

Setting roles up once, early

Roles are easiest to assign correctly when a workspace is first set up, before licenses have piled up unassigned or ended up with the wrong default owner. Going back later to fix roles after the fact is possible, but it’s a cleanup task — deciding them up front is just a decision.

A small team doesn’t mean no roles

Even a two- or three-person operation benefits from this — the owner handling billing and the field staff renewing licenses are already different jobs in practice, whether or not the software enforces the distinction. Setting roles up early means that distinction is already in place by the time the team grows and the difference starts to matter more.

How this differs from simply hiding a menu item

Roles here aren’t a matter of what buttons a person happens to see — a staff account genuinely can’t perform an owner-level action, even if they knew the exact steps to try. That’s a meaningful difference from a UI that just doesn’t show a link: it means the access boundary holds even for someone who knows exactly what they’d want to do if they could.

Where ContractorLicenseAlert fits

Teams and the directory

What happens when someone leaves the company

More on renewals

How to keep track of contractor license expiration datesExpiration dates hide in PDFs, wallets and inboxes. A simple system for recording every license, permit and certificate — and hearing about each renewal in time.Renewal lead time: why reminders should start earlyThe expiration date is when it’s too late. Here’s how to work out when a renewal needs to begin — and why that’s the date your reminders should count down to.Moving your license list out of a spreadsheetA spreadsheet is a fine place to start and a poor place to rely on. A checklist for tidying it up and moving it into a system that sends reminders for you.What gets read automatically from a license document, and where you still checkOCR and AI can read an expiration date off a license, permit or certificate — but not every document, and never without you confirming it. What the extraction does, and doesn’t do.A certificate of insurance with more than one policy: how it becomes separate licensesA single COI often lists general liability, workers’ comp and an umbrella policy together. Here is how each one is read out and saved as its own tracked record.When an expiration date can’t be read, and why that’s better than a guessSome bonds and permits simply don’t carry a fixed end date. Why the extraction leaves the field blank instead of inventing one, and what to do with it next.Tracking surety bonds alongside licenses, not in a separate spreadsheetA bond is easy to forget because it rarely comes up day to day. Keeping it in the same system as your licenses, with the same reminder discipline, is what keeps it from lapsing quietly.General liability vs workers’ comp: two different renewal clocksThey’re often asked for together, but a general liability policy and a workers’ comp policy don’t run on the same schedule. Tracking them separately is what keeps one from lapsing next to the other.What happens if a subcontractor’s certificate of insurance lapses mid-jobA sub’s coverage is only as current as the certificate you’re holding. How to collect, track and renew subcontractor COIs without chasing it over email every time.Tracking licenses for people who don’t need a loginA subcontractor or seasonal hire doesn’t need an account to be reminded about their own license. The people directory, and how reminders reach someone outside your workspace.What happens to a license’s reminders when someone leaves the companyRemoving a team member shouldn’t mean their licenses go quiet too. What actually happens to access and reminders the moment someone is taken off a workspace.Email digest or one at a time: choosing how renewal reminders arriveSix people on a license doesn’t have to mean six separate emails every time. The choice between individual reminders and one daily digest, and when to use each.Why an overdue license gets a different subject lineOnce a renewal deadline passes, the reminder itself changes, not just the schedule. What the overdue follow-ups look like and why the subject line calls it out.Setting up a renewal calendar your whole team can checkA shared calendar view beats everyone keeping their own list. How the dashboard’s status buckets and two calendar views work.How often different license types actually renew: 12, 24 and 36 months comparedNot every license runs on the same clock. How the product’s default notice windows and terms differ across contractor licenses, permits, insurance, bonds and certifications.Continuing education hours: tracking certifications that expire on training, not just timeA certification can lapse even before its date arrives, if the hours behind it haven’t been completed. How to track CE requirements alongside the expiration date.Collecting renewal documents from a vendor without giving them a loginYou don’t need to create an account for every subcontractor or vendor just to get a current document from them. How an upload link works, end to end.Four reports every contractor compliance review actually needsCompliance, expiring, reminder delivery and activity — the four report types cover what most reviews ask for, and all four export to Excel or PDF.What an audit log should show when a license gets deletedDeleting a license should leave a trace, not a gap. What the activity log records, and why deleting one asks for a fresh login code first.Checking whether a license is actually active: state lookup tools by tradeA tracked expiration date tells you what your own records say, not what the licensing board’s records say. Where to actually check, trade by trade.

Put your next renewal on the radar.

Try everything free for 7 days. No card needed.

Start free trial Continue to workspace See pricing

Then $39 a month, or $390 a year. Cancel whenever.