My Jobs Toggle
The My Jobs / All Jobs segmented toggle narrows All Jobs and Analytics to the jobs you're listed on as PM. It's on by default for PMs and doesn't appear at all for viewers.
The Getting Started chapter has a friendlier introduction at My Jobs vs. All Jobs. This page is the deeper reference: matching rules, global state across pages, count labels, viewer behavior, and how the toggle composes with Company and PM chips.
Toggle on = your jobs only. Toggle off = every job.
Where the toggle lives
| Page | Toggle visible? |
|---|---|
| All Jobs | Yes (PMs only) |
| Analytics | Yes (PMs only) |
| Action Queue | No — page is implicitly scoped to you at the data layer |
| Job Detail | No — already scoped to a single job |
The toggle sits at the top of the page, to the left of the Company and PM chip filter rows.
What you see
Two buttons in a single segmented pill:
My Jobs (N)— N is the count of jobs assigned to you in the current dataset.All Jobs (M)— M is the total count of jobs in the page's dataset.
The active side shows blue with white text. The other side stays white with gray text. Click either to flip.
Default state
- PMs — toggle defaults to
My Jobson every fresh sign-in. - Viewers — toggle doesn't render at all. The page always shows All Jobs.
The page knows you're a PM by matching your sign-in to a PM account. Sign in as a non-PM and the toggle isn't even in the page.
One toggle, two pages — global state
The toggle is global, not per-page. Flipping it on All Jobs also flips it on Analytics, and vice versa. Flipping it on either page also keeps that state across navigation between them — flip it on Analytics, navigate to All Jobs, and All Jobs is in the same state.
This is intentional: PMs almost always want the same scope on both pages. The toggle reads from a single setting on your sign-in session.
If you flip the toggle to All Jobs on Analytics, scroll, drill into something, then click into All Jobs from the navbar — All Jobs opens in All Jobs mode too. The toggle's state has followed you across the page boundary.
No persistence between sessions
Refreshing the browser resets the toggle to its default (My Jobs on for PMs). Signing out and back in does the same. The toggle does not remember a setting from a previous session.
The matching rule, in plain English
A job appears under My Jobs when your account is on the list of PMs assigned to that job. The matching is account-based, not name-based: the system checks the translated PM-account list on each job, not the raw text of the PM field.
This matters because the PM field on a job can hold a mix of accounts and free-text names. A job with a first-name PM string ("Jared", not the account) won't match the toggle. See My Jobs vs. All Jobs for the workaround in detail and Troubleshooting for the "I don't see my jobs" pathway.
Jobs with a first-name-only PM field WILL NOT appear under My Jobs. The toggle matches on the underlying PM account, not on a typed-in name. If a job is assigned to you but the PM was typed in as just your first name, the toggle won't pick it up. You'll need to find it via global Search or by toggling off and scrolling. See Troubleshooting for diagnostic tips.
Multi-PM jobs
A job with two assigned PMs appears for both of them. The toggle matches "your account is in the list," not "your account is the only one in the list." Co-managed jobs show up cleanly for everyone on the assignment.
The toggle versus the green + My Jobs chip-button
These two controls look similar and live near each other, but they do different things:
| Control | Where it lives | What it does |
|---|---|---|
| My Jobs / All Jobs toggle | Above the filter chip rows | Global switch. Two buttons, one active at a time. Scopes the whole page by your account. |
Green + My Jobs chip-button | Inside the PM filter chip row | Adds you as one entry in the PM multi-select. Useful when you want "my jobs PLUS a colleague's jobs." |
Don't confuse the toggle with the chip-button. The toggle is global and exclusive (you OR everyone). The chip-button is additive (you, plus whatever else is in the PM row). The chip-button hides itself once you're already in the PM selection. See Company and PM Filters for the chip-button.
The intersection case: when the toggle is on AND a PM chip is active, the page shows the intersection — your jobs that are also matched by the PM chip. With most colleagues, that intersection is empty (you don't co-manage their work). It's only useful when you genuinely co-PM with the chipped person.
Composing with Company and PM chips
Chip filters apply on top of the toggle. The composition is straightforward:
- My Jobs on +
Company: PSS→ your PSS jobs only. - My Jobs on +
Company: PSS+Company: PSW→ your PSS or PSW jobs. - My Jobs on +
PM: Hailey→ jobs that are yours AND assigned to Hailey (often empty, unless you co-PM with her). - My Jobs off +
PM: Hailey→ all of Hailey's jobs, regardless of who you are.
For the AND/OR rules in detail, see Company and PM Filters.
Action Queue — implicitly self-scoped
Action Queue doesn't have the toggle. It doesn't need one — the queue is scoped to the signed-in user at the data layer, so the only way Action Queue can show items is for the rows assigned to you.
There is no way to view another PM's Action Queue from the dashboard. If a colleague is behind on their own queue, that's between them and the queue — there's no escalation path through the dashboard.
The Company filter still works the full way on Action Queue. The PM filter is locked to you (covered on Company and PM Filters).
Viewers see no toggle
If you're signed in as a viewer rather than a PM, the toggle doesn't render anywhere. You always see the All Jobs view. The toggle is a personal-scope mechanism, and there's no personal scope to apply when you don't own jobs.
See Companies and Access for who is a PM versus a viewer.
The count in the button label
The numbers in the button labels — My Jobs (14), All Jobs (3712) — count jobs in the page's current dataset. They reflect the most recent dataset refresh, which can be up to four hours old. See Data Refresh Rates.
If you apply Company chips, the All Jobs count narrows accordingly. The My Jobs count narrows the same way.
Quick reference
| Question | Answer |
|---|---|
| Is the toggle the same on every page? | Yes — flipping it anywhere flips it everywhere it appears. |
| Does it remember between sessions? | No — every fresh sign-in starts at the default (My Jobs on for PMs). |
| Will it find jobs assigned by first name? | No — only by account. Use Search or toggle off. |
| Where is it on Action Queue? | It isn't. The queue is implicitly scoped to you. |
| Where is it on Job Detail? | It isn't. Job Detail is already a single job. |
| Where is it for viewers? | It isn't. Viewers always see All Jobs. |
Related
- Company and PM Filters — the chip filters that compose with the toggle, including the green
+ My Jobschip-button (a different control) - Drill-Down Chips — chips emitted by widgets, not by the toggle
- Filter Banner — the bottom banner that mirrors Company and PM chips (the toggle does NOT render there)
- My Jobs vs. All Jobs — the friendly introduction; covers the messy-name-data workaround in detail
- Companies and Access — who is a PM versus a viewer
- Action Queue Overview — explains the implicit self-scoping on the queue
- Troubleshooting — "I don't see my jobs" pathway
- Data Refresh Rates — for the count refresh cadence