Workstream scope: a supervisor who runs only their own workstreams

A reactive-repairs supervisor should run reactive repairs, not wander through the metering programme's jobs, routes and shifts. Workstream scope does that: a person can be limited to the workstreams they manage, and nothing outside them shows up at all.

Setting it on a person

Open the person in Users, choose View full profile, then Edit access. Once they hold Manage jobs or Manage schedule, a Jobs and schedule cover field appears below the permission chips: "A person limited to the workstreams they manage sees no other jobs, routes or shifts."

• All workstreams: the whole operation.
• Only workstreams they manage: then tick the workstreams they manage. With none set up yet: "No workstreams yet. They can create their own, which they will manage automatically."

Changing this needs Manage access. Workstream scope is on the Crew plan and above; a workspace already using it keeps it.

Supervisor is the profile built around this. Choosing Supervisor in Invite user or in Edit access & role sets Only workstreams they manage for you. A supervisor added through Add several users, a spreadsheet import or an approved join request starts on All workstreams instead, so open Edit access and narrow them afterwards. What a supervisor can do is set by their chips; see Access profiles and permissions.

Naming managers on a workstream

The other half of the setting lives on the workstream. On the Jobs page, choose the gear (Manage workstreams), edit the workstream, and scroll to Managers: "People limited to the workstreams they manage see this one only if they are named here." Creating a workstream makes you one of its managers automatically. See Workstream settings.

What a scoped person sees

• Jobs, routes, shifts, route batches and the dashboard all narrow to their workstreams. A job with no workstream at all is outside every scope; only someone on All workstreams sees those.
• Something outside their scope isn't forbidden, it's not found, the same as a record that never existed. Saying forbidden would confirm it exists.
• A scoped person with no workstreams named sees nothing, not everything. Name at least one.
• People aren't scoped. A scoped scheduler still picks from the whole team when covering a shift. Scope limits which work they see, not who they can put on it.

Clients, sites, fleet, forms, users and the rest follow the ordinary permission chips. Time follows scope too: see below.

Time in their workstreams

A scoped person who also holds Manage time clock sees time the same way. Timesheets, the Today board, change requests and submitted timesheets show them a person for a period when that person clocked at least one shift in their workstreams. They then see that person's whole sheet, so the totals match what the person and the office see. Shifts the person worked in another workstream show their times as Another workstream, with no job, site, note or location, and nothing to act on.

• They can edit, remove or approve only shifts in their workstreams, and can't move a shift onto another workstream's job.
• A week, a change request or a corrected week that also holds time from another workstream is decided by someone who manages every workstream: "This week has time outside your workstreams, so someone who manages every workstream decides it."
• An export holds only their workstreams' shifts.
• Locking or unlocking a period needs someone who manages every workstream.
• The dashboard's time cards, such as Hours clocked, On the clock now and Missing clock-outs, count only time clocked in their workstreams.

Time clocked on a site, or on no job at all, is outside every scope.

Work they're scheduled on

Scope limits what someone manages, not the work they're sent to do. If a scoped supervisor is on a published shift for a job in another workstream, they can still file forms, evidence and defects against that job while the work is unfinished, and for seven days after the visit is marked finished, even if the office closes the job in the meantime. A visit finished today moves straight to the past list on their Work tab, where they can still capture against it. Other jobs in that workstream stay hidden, and a draft or cancelled assignment doesn't open anything.

Tip: scope is enforced on the server for every screen, export and search, not just the menu. If a supervisor reports a job as "missing", check the job's workstream and that workstream's Managers first.