Why pilots should only see the jobs they're assigned to

Most drone teams run a mix of work: a critical infrastructure inspection for one client, a marketing shoot for another, a survey for a third. Each job comes with its own confidentiality terms — and often a site-specific NDA on top of the master agreement.

If your operations tool lets every pilot browse every project, you've already broken those terms. Not maliciously — just by default.

Role isn't enough

A simple role system ("pilot can log flights, manager can edit projects") doesn't help here. The pilot needs some access to log flights and read job briefs. The question is which jobs.

The answer has to be explicit assignment: a pilot sees only the jobs they have been assigned to, and only the projects those jobs belong to. Nothing else in the workspace is visible to them — not project names, not client lists, not other pilots' flight logs.

The same applies to Operations Leads: they see only the projects they own, not the whole workspace pipeline.

How it works in FlybyOps

Five built-in roles per workspace, with project- and job-scoping layered on top of the base role:

• Root — workspace admin
• Project Manager — sees the whole workspace
• Operations Lead — sees only assigned projects
• Pilot — sees only assigned jobs (and the parent project for context)
• Ground Staff — same scoping rules as pilots

When a pilot opens the dashboard, they see a list of jobs they're on. That's it. No project picker, no client browser, no cross-job leakage. The audit log records every access, so if something does need to be reviewed later, the trail is complete.

This isn't a UI nicety — it's the only way a regulated drone program can honour the confidentiality terms its clients are paying for.