Most field-service CRMs treat every technician like a permanent software user.

I never liked that model.

A tech may only need access to one job, one customer, for one period of time. Why should that require giving them a permanent account with ongoing access to the company's CRM?

So with Chameleon-CRM, I built it differently.

When a job is dispatched, the technician can receive a secure Magic Link and access PIN by email.

That gives them access to their technician workspace where they can see what they actually need for the job — customer/job information, dispatch details, photos, notes, status controls, and the tools needed to complete the work.

They don't need a traditional CRM username/password.

And the important part:

When the job is over, the business can revoke that access.

The workflow becomes:

Create job → Dispatch tech → Send temporary access → Tech completes work → Revoke access

The technician's ability to work in the field doesn't mean they need permanent access to the company's entire business system.

I also deliberately separated this from employee/time-clock access. If someone is actually an employee who needs payroll and time tracking, they're managed accordingly. Being dispatched to a job doesn't automatically make someone a permanent internal CRM user.

This has turned into one of my favorite parts of building Chameleon-CRM because it changed the question from:

"What role should this user have?"

to:

"What does this person need access to right now?"

That's a much more interesting way to think about fieldservice software.

I'm curious what other people running service businesses think about this approach.

Would you rather give every field tech a permanent CRM account, or give them access only when there's actually work assigned to them?