Reporting Dashboard

Control Wranker Reporting Dashboard settings without report chaos.

Wranker Reports Settings turns scattered admin decisions into one governed policy layer for content availability, white-label assets, export defaults and sharing permissions.

  • ✓ Admin-only governance
  • ✓ Content availability matrix
  • ✓ PDF and CSV export rules
  • ✓ White-label boundaries
Placeholder proof logo — replace
Placeholder policy quote — replace
Placeholder agency badge — replace
Wranker Reporting Dashboard Settings for Report Governance previewWranker Reporting Dashboard Settings for Report Governance preview
The old way

Reporting breaks down when policy lives in memory, old decks and Slack threads.

Every reporting team eventually asks the same questions: why is this section missing, which branding should be used, how many rows are in the PDF, and can this report be shared outside the client domain?

  • —Unclear global vs per-report scope
  • —Manual white-label edits
  • —Hidden export constraints
  • —Risky sharing defaults
Fragmented policy workflow
Template sections disappear
PDF limits surprise clients
Branding lives in old decks
External share modes stay open
Admins cannot explain gates
Per-report and org rules blur
Builder shows blocked panels
Exports lack data source notes
No saved-by audit snippet
Result without governed settings
?
Policy owners
Hidden
Export rules
At risk
Client trust
Structural counts from the Reports Settings and Reporting Dashboard V1 specs. Replace with verified customer governance benchmarks when available.
THE POLICY LOOP

From scattered decisions to governed reports in five steps.

Reports Settings is not a static admin page. It is the policy loop that tells templates, the Builder, exports, live links, schedules and sharing what is allowed.

GLOBAL VS PER REPORT

The first job of Reports Settings is removing ambiguity.

The org/admin surface and the per-report surface must never look interchangeable. Wranker turns that distinction into visible product language.

ORG / ADMIN

Reporting Settings (Org)

Admin-only global policies for all reports and templates. This is where the content matrix, white-label rules, export defaults and permissions live.

AdminGlobalApplies to all reports
PER REPORT

Report Settings

Per-report controls that belong to one report, such as mapping, schedule, export and access settings for that specific report.

Report scopedPer reportUses report name
SURFACE CLARITY

Make global reporting policies impossible to confuse with per-report controls.

Reports Settings starts with the most important governance decision: separating org-level policy from report-specific configuration. Wranker keeps the admin surface labelled as Reporting Settings (Org), shows an Admin badge, and makes clear that these policies apply to every report and template.

Teams use one generic settings label and later discover that a change affected more reports than expected.
Wranker separates global Reporting Settings (Org) from per-report Report Settings with explicit UI context.

Reporting settings identity

Global policy and report controls stay visibly separate.

Admin only
Organisation policy surface
Reporting Settings (Org)
Global
Scope
Organisation-wide
Report context
None required
/reporting/settings
No report picker. No report name.
Saved policy publishes to Templates, Builder, Exports and Sharing.
Clear scope boundary
Per-report surface
Report Settings
Executive SEO — Sept · wranker.com
Per report
/reporting/reports/rep_123/settings
CONTENT AVAILABILITY

Govern which dashboards, panels and sections appear in reports.

The Content Availability matrix is the core mechanism behind governed report creation. Admins can decide whether each dashboard, panel and tab or section is Enabled, Hidden or Admin-only, then template previews and the Builder Section Picker respect that policy.

Report sections disappear through manual edits, copied templates or hidden team conventions that are hard to explain.
Wranker turns report content access into a visible three-level policy matrix with search, bulk actions and previews.

Content availability matrix

Set report section access before Builder.

Admin only
Content availability
Three-level policy matrix
Org rule
Dashboard / panel / sectionPolicy
SEO Dashboard
Dashboard
Enabled
Rank Tracker
Panel
Admin-only
Winners / losers
Section · from Rank Tracker
Inherited
Site Audit
Dashboard
Enabled
Page Experience
Panel
Hidden
Parent restrictions cascade safely.
Template previews and Builder skip gated sections.
Template preview
Builder respects org policy
GSCGA4
Executive Monthly SEO
Top pages
Available
Rank moves
Admin-only
CWV panel
Skipped
28
Enabled
9
Gated
3 pending policy changes
Saved by Priya · 08:45
WHITE-LABEL POLICY

Keep client-facing branding consistent without polluting report blocks.

White-label settings belong at the org level because they affect exported PDFs and live report links across the team. Wranker keeps the boundary clear: logo, website and support details appear in headers, footers and live-link chrome, not inside the data canvas blocks.

Branding is added manually to slides or pasted into report content, making exports look inconsistent across clients.
Wranker uses org-level white-label settings for export and link chrome while preserving clean report panels.

White-label policy

Client branding stays consistent without changing report panels.

Admin only
Org brand kit
White-label assets
AC
Acme Growth
Logo · site · support
Logo placement
PDF header + footer
On
Website URL
acmegrowth.com
On
Support email
support@acme.com
On
Support phone
+44 20 0182
On
Colour override
Locked for Phase 1
Locked
Report chrome preview
Header and footer only
Live link
A
Acme report
acmegrowth.com
Client view
Monthly SEO report
Clicks
42.8K
CTR
4.8%
support@acme.com+44 20
Canvas blocks stay clean
Branding stays outside data panels.
2 pending brand changes
Saved by Priya · 08:46
EXPORT DEFAULTS

Set PDF and CSV rules before teams hit export.

Reports Settings makes export behaviour predictable. Admins can set paper size, orientation, filter handling, footer tokens and hard limits such as PDF table rows while keeping CSV as the complete dataset export path.

Clients ask why exported PDF tables are truncated, while teams scramble to explain which filters and rows were included.
Wranker shows export defaults and limits as policy, then repeats the rules inside Builder and delivery flows.

Export defaults

PDF and CSV rules are set before teams export.

Admin only
Org export defaults
PDF and CSV behaviour
Saved
PDF defaults
Client PDF
A4 · portrait
Paper size
A4
Margins
Standard
Respect filters
On
CSV defaults
Dataset export
Full filtered rows
Row output
Full
Headers
Included
Format
UTF-8
PDF tables: 100 rows · CSV keeps full filtered rows.
Builder export hint
Date and Source tokens stay visible.
PDF tables are limited to 100 rows; use CSV for the full dataset.
Preview
SEO.pdf
A4CSV
filters respected
3 pending export changes
Saved by Priya · 08:48
PERMISSIONS

Turn reporting access into visible, policy-driven UI.

Reporting permissions should not rely on training or memory. Wranker lets admins set org-level gates for creating templates, sharing outside a domain and scheduling reports, then downstream interfaces reflect those restrictions before users take risky actions.

Users discover a policy only after a failed share, a blocked schedule or an accidental external link.
Wranker reflects org policy in Share, Template Library, Schedule and Builder actions before risk reaches the client.

Reporting permissions

Access rules surface in every report action.

Admin only
Org permissions
Reporting access gates
Saved
Create templates
Owner and Admin roles only
Admin
Schedule reports
Editors can request approval
Review
Share outside domain
External domains are blocked
Blocked
Internal viewers
Workspace users can view links
Allowed
Full CSV export
Admin confirmation required
Approval
Policy shows before risky actions
Share, schedule and template controls inherit org rules.
Action preview
Disabled states explain why
Executive SEO report
wranker.com only
Team link
OnViewer access
Schedule
LockedAdmin review
External share
OffBlocked by policy
5
Policy gates
2
Locked actions
2 pending permission changes
Saved by Priya · 08:49
DOWNSTREAM IMPACT

One setting should explain every downstream report behaviour.

Reports Settings is valuable because it makes the rest of Reporting predictable. The same policy explains what appears in templates, what the Builder can use, how exports behave and which sharing modes are allowed.

Template Library

Template previews

Show disabled-section notices before a user creates a report from a governed template.

Report Builder

Builder Section Picker

Only expose sections and saved panels that the org policy allows for that user.

Exports

Export dialogs

Repeat PDF row caps, CSV full-row rules, footer tokens and respect-filter defaults at the moment of export.

Permissions

Share workflows

Disable restricted live-link modes, external recipients or schedule actions directly in the downstream UI.

WHO IT IS FOR

Reporting governance for specialists, teams and agencies.

The same settings layer helps a solo SEO avoid messy exports, helps in-house teams enforce safe sharing, and helps agencies scale white-label reporting across client portfolios.

Placeholder testimonial — replace with customer proof
“We stopped explaining report exceptions after every delivery because policy became visible before the report was built.”
OPS
SEO operations lead
Placeholder persona — replace after customer interview
Placeholder metric — replace with verified benchmark
12 → 1

Example narrative only: scattered report policy locations reduced into one global admin surface. Replace with measured customer operations data before publishing as proof.

Use this card for a verified before/after governance metric once available.
OLD WAY VS WRANKER WAY

Replace hidden report rules with a visible policy system.

Reports Settings turns admin choices into governed product behaviour across templates, Builder, exports, sharing and scheduled delivery.

WorkflowWithout WrankerWith Wranker
Clarify settings scopeAdmins and editors guess whether a setting is global or only for one report.Wranker separates Reporting Settings (Org) from per-report Report Settings with labels, badges and route context.
Control report contentTeams hide sections by deleting blocks, which creates broken templates and inconsistent report structure.Use a three-level Content Availability matrix for dashboards, panels and sections with Enabled, Hidden and Admin-only states.
Apply white-label rulesBranding gets copied into slides and can appear inconsistently inside report content blocks.White-label assets apply to PDF headers/footers and live-link chrome, while canvas blocks remain clean and data-focused.
Set export expectationsUsers do not know why a PDF table is cut off or whether CSV includes all rows.Export policy explains PDF row caps, CSV full rows, paper size, filter behaviour and footer tokens before delivery.
Enforce sharing rulesUsers can expose reports outside approved domains before policies are visible in the UI.Org permissions visibly disable restricted share modes, template creation and schedule actions where policy blocks them.
Audit admin changesPolicy changes happen without a clear save model or record of who changed what.Settings use local edits, Save/Cancel, a sticky footer and saved-by audit snippets for safer governance.
Start governed reporting

See how Wranker can turn SEO reporting into a governed client delivery system.

Start with your SEO audit, then explore how templates, Builder, scheduled reports, white-label exports and Reports Settings fit together.

Risk reversal
✓No credit card required to start the audit flow.
✓Connect GSC and GA4 when ready.
✓Keep PDF, CSV and live-link rules explicit.
✓Use white-label controls across report delivery.
✓Scale from one report to agency governance.
RELATED WRANKER FEATURES

Reports Settings works best beside the full reporting system.

Use these related feature pages to connect governance with report creation, white-label delivery, scheduling, templates and agency workflows.

FAQ

Questions teams ask before centralising reporting policy.

Direct answers for SEO, AEO and GEO discovery around Wranker’s Reports Settings and Reporting Dashboard governance.

What are Wranker Reporting Dashboard settings?
Wranker Reporting Dashboard settings are the org-level controls for reporting governance. They let admins manage content availability, white-label assets, export defaults and permissions that apply across reports, templates, the Builder, exports, sharing and scheduled delivery.
Is Reports Settings the same as per-report Report Settings?
No. Reports Settings refers to the global Reporting Settings (Org) admin surface. Per-report Report Settings are scoped to one report and should show that report’s name, mapping, schedule, export and access controls.
Who should use Reports Settings?
Reports Settings is primarily for admins, agency owners, SEO operations leads and team managers who need to control what reporting content is available, how reports are branded, what export rules apply and who can share or schedule reports.
What does the Content Availability matrix control?
The Content Availability matrix controls dashboards, panels and tabs or sections. Each level can be Enabled, Hidden or Admin-only, and child items inherit restrictions from parent items so report templates and the Builder stay governed.
Where does white-label branding appear?
White-label assets appear in exported PDF headers and footers and in live-link chrome. They do not appear inside the report canvas blocks, which keeps reporting content clean and consistent.
Can admins control PDF and CSV export rules?
Yes. Admins can set PDF defaults such as paper size, orientation, margins and respect-filters behaviour. Wranker’s Phase 1 rules also make PDF table limits clear while CSV keeps full filtered rows.
Can Reports Settings prevent external sharing?
Yes. Org-level permissions can disable or grey out restricted share modes such as external sharing or anyone-with-link options. The UI should explain why the action is blocked and which admin policy is enforcing it.
How do Reports Settings affect templates and the Builder?
Content Availability changes affect template previews and the Builder Section Picker. If a section is hidden or Admin-only, template previews can show a disabled-section notice and the Builder skips blocked content instead of creating broken placeholders.
Is this feature useful for agencies?
Yes. Agencies can use Reports Settings to standardise report governance across clients, protect white-label presentation, enforce export rules and keep client-facing sharing aligned with agency policy.

Keep every report policy clear, consistent and client-safe.

Bring content gates, export rules, white-label delivery and sharing permissions into one predictable Wranker reporting workflow.

  • No credit card
  • Quick setup
  • Cancel anytime
  • Scale when ready
Ready to govern reporting before delivery?