The Lead Settings hub

What this page is — the entry point to lead configuration: eight sections holding everything you can change about how leads behave.

What it is for — knowing which section owns what, and which permission reveals each one.

The problem it solves — getting in. The hub is gated on the source permission rather than a settings permission, so a role that administers pipelines and queues can be locked out of the screen containing them. This page says what to grant, and why the Rules section is visible to everybody whether it should be or not.

Route: /org/marketing/leads/settings · Gated on: Manage Lead Sources Module: mkt_leads_settings — 1 permission (Show Lead Settings in the header settings menu., the gear-menu entry)

Figure 1 — All eight sections, as an org admin sees them. 1 Lead Sources · 2 Pipelines & Statuses · 3 Lead Queues · 4 Rules · 5 Custom Fields · 6 Agents · 7 Master Data · 8 Webhooks.

---

1. The eight sections

#	Section	Covers	Revealed by
1	Lead Sources	Sources	Manage Lead Sources
2	Pipelines & Statuses	Pipelines and statuses	Manage Lead Pipelines
3	Lead Queues	Queues	Manage Queues
4	Rules	Scoring · assignment · conversion	always visible — see section 3
5	Custom Fields	Custom fields	Manage Lead Pipelines
6	Agents	Agents	View lead agents list
7	Master Data	Source categories · grades	sourcecat.view or grade.view
8	Webhooks	Webhooks	View API keys and logs

Figure 1 shows the maximum surface

Sections are hidden individually. A role with fewer permissions sees fewer sections, and that is correct behaviour, not a broken screen. Custom Fields is revealed by the pipelines permission, which is not obvious from its name.

---

2. Getting in

Any one of the section permissions opens the hub

You do not need the whole set. Holding any one of the section permissions in the table above is enough to get in, and you then see only the sections you can use.

A role with none of them is refused with "You do not have permission to manage lead settings."

---

3. The Rules section is always visible

Each section appears only for a role that can use it

The Rules section needs one of Manage Lead Scoring Rules, Manage Lead Assignment Rules or Manage Conversion Rules for Lead to Contact or Deal. A role holding none of the three does not see it.

Figure 2 — The Rules section and its five sub-tabs, all visible regardless of permissions.

---

4. Navigating by URL

Param	Reads	Example
?tab=	The section	?tab=pipelines
?rule=	The Rules sub-tab	?tab=rules&rule=scoring

Only ?tab= is understood by the in-app documentation button

The Docs button maps a screen to a documentation page using ?tab= alone. Every ?rule= sub-tab therefore resolves to the same page, which is why the rules pages cross-link each other explicitly.

---

5. The hub is full-screen

This is a SettingsHubShell screen: it hides the application header, so the project chip is not reachable from here. Select the project before entering, and use Exit Lead Settings at the foot of the rail to leave.

---

6. Don't confuse this with…

This	Not this
Lead Settings	Deal Settings at /org/marketing/deals/settings
Section 3, Lead Queues — configuring	The Queues tab on the list — working
Master Data	Custom Fields. Master Data is source categories and grades

---

7. Troubleshooting

Symptom	Cause
Cannot open the hub	Missing Manage Lead Sources. Section 2
Access Denied inside the hub	Holding none of the four gating permissions. Section 2
Fewer sections than a colleague	Sections are permission-gated. Section 1
Custom Fields missing	It needs manage_pipelines. Section 1
No project chip	The hub hides the header. Section 5