Where to find them | Sidebar → Access (General Access) and Admin (the rest) |
Who can see them | Leadership. Analytics is super-admin only. |
Can you change data here? | Yes — access levels, and the job-description sync |
How fresh is it? | Access changes apply on the person's next session; usage data is live |
Signal exposes sensitive data — client revenue, salaries, churn predictions. These four screens govern that exposure.
General Access
What it's for
Granting and revoking Signal's access levels, person by person. Least privilege by default: a new person starts with nothing and you add only what they need.
What you'll see
Everyone who has ever signed into Signal, with their name, email, when they first signed in, their current level, and toggles for each level.
Plus counts of total users and admins, and a badge showing which email domains may sign in at all.
How to use it
A new leader needs access. Have them sign in once with their work Google account — that creates their record. Then search their name and turn on what they need: Team Lead for Manage Leads and Client Pulse, Admin for capacity, profitability, targets and corrections, Gandalf for the back office, P&Ls and AI Solutions.
Right-size existing access. Read down the list periodically. Someone who changed roles a year ago may still hold what that role needed.
Remember what this screen does not control. Compensation data is granted separately on Growth Access by a designated Growth manager. Turning on every toggle here grants no salary visibility at all.
About the tier names
Two of Signal's levels have internal nicknames you'll see on this screen:
Gandalf — the leadership tier. Unlocks the back office, Divisional P&Ls, Census and AI Solutions.
Sauron — the super-admin tier, held by the Signal team. Included automatically in everything, can't be turned off from this screen, and is the only tier that can open Analytics.
Account Directors and Group Directors are moved up to Team Lead automatically the first time they sign in, based on the clients they own in Nova.
Good to know
Changes apply on the person's next session. Ask them to reload or sign out and back in. Your own row updates immediately.
Super-admin rows can't be demoted here — that's deliberate, so the platform owners can't be locked out.
"Last Active" is not reliable. The column exists but nothing currently keeps it up to date, so it may read "Never" or show a stale date. Don't use it for offboarding decisions. "First Sign In" falls back to when the record was created.
Growth access is a separate system. See Growth Access.
Assignment History
What it's for
The audit trail for team and revenue-split changes made in Signal. "Who moved this client off my roster?" becomes answerable in seconds.
What you'll see
The most recent changes, each showing who made it, when, and a before-and-after comparison with names resolved. Filterable by type and searchable by client.
How to use it
Someone says a client vanished from their book. Search the client name, expand the row, and you have who changed the team, when, and exactly what changed. Then revert it on Manage Leads if it was wrong.
Good to know
It only records changes made through Signal. An assignment changed directly in Nova won't appear here. That's the single most common reason a change seems to have no author.
It shows the most recent few hundred entries. Older history exists but isn't displayed.
An unrecognized ID appears as a number when the person or client can't be resolved to a name.
JD Sheet Sync
What it's for
Refreshing the mapping between people, job titles and job-description documents — the mapping behind the JD links on employee pages.
How to use it
When job descriptions are updated and employee pages still link to the old documents, open this and click Resync. Then check the counts, and look at the conflicted-titles list.
If it fails with a permission error, the screen tells you the fix: share the source sheet with the service-account address it displays, using the copy button provided.
Good to know
The sync only lives in memory. After any deployment or restart, Signal reverts to a built-in snapshot until someone resyncs. The status card tells you which mode is active — worth checking before concluding the links are broken.
A title in the conflicted list needs per-person rows in the sheet, because different people with that title point at different documents. Signal won't guess.
The same title mapping also drives KPI target matching. See KPI Targets.
Analytics
Super-admin only. It shows raw usage for every user, so even leadership access doesn't include it.
What it's for
Measuring whether Signal is actually used, and whether the prediction tools produce action rather than just page views. This is the build-to-usage gap made measurable.
What you'll see
Headline counts — total events, unique users, top page, top action, over your chosen range
Activity over time, with a line per module
Top users, and top pages and actions
Adoption by division
Usage by client risk — client-scoped activity bucketed by the client's risk band
Actions on flagged clients — of the recommended actions currently marked as taken, how many were on high or critical-risk clients
That last one is the closest thing Signal has to an outcome measure for the prediction tools.
How to use it
Weekly, set the range to seven days. Check unique users and adoption by division against the weekly-active goal. Then check actions on flagged clients — are the churn and expansion tools producing action on high-risk clients, or only page views? Use top users to work out who to enable next.
Good to know
It counts only what's instrumented. Page views are logged everywhere, but detailed feature actions exist mainly in the churn, expansion and portfolio areas. Treat trends and comparisons as reliable, and absolute totals as a floor.
Very long ranges can undercount, because there's a cap on how many events are fetched per range.
Risk bands are point-in-time. Usage is credited against the risk band as of the week the event happened, not today's — so these numbers deliberately won't match the current Churn Risk page.
"Unknown" in adoption by division means the email didn't match an active person — departed staff, service accounts, or a mismatched address. The card shows how complete the match was.
Enrichment panels degrade honestly. Adoption by division, usage by client risk and actions on flagged clients show an explicit unavailable state rather than zeros when their lookups fail. A zero means zero; an unavailable message means unknown.
New instrumented features show a raw name until a friendly label is added.
Common questions
Why do I get redirected to Summary from these pages? They need leadership access. See Who can see what.
Why can't I open Analytics? I have leadership access. Analytics is super-admin only, because it shows usage logs for every individual. Adding someone requires a change by the Signal team, not a toggle.
How do I give someone access to salary data? Not here. Use Growth Access — and note leadership access doesn't include the ability to grant it.
A client disappeared from someone's book. Who changed it? Search Assignment History. If nothing appears, it was changed directly in Nova rather than in Signal.
JD links are stale. Resync on JD Sheet Sync. Remember the sync resets after each deployment, so it may need doing again.
Why does a client's risk band in Analytics differ from Churn Risk today? Analytics uses the band as of the week each event happened, on purpose, so usage is credited against what the person actually saw at the time.
Can I trust "Last Active" on General Access? No. Nothing keeps it current. Don't offboard on it.
Related
Who can see what — the access model in plain language
Growth Access — the separate system for compensation data
Manage Leads — what Assignment History records
Corrections — the data-quality queue, also in the Admin section
Recruiting & Hiring Pipeline — Hiring Pipeline now lives under Talent