How to Hide Full Report, Grid Edit, and Email on Embedded Quickbase Reports

People building locked-down Quickbase experiences with iForms (or any read-only role) often embed a report on a form so users only see the rows they need. The catch, raised again in this community thread, is the toolbar that still sits on top of that embedded report: Full Report, Grid Edit, Email, and More.

There is still no form setting that turns that whole bar off on a Report Link. Role permissions can clear some of the actions, but Full Report on a classic Report Link embed usually stays. The cleaner lock-down is to stop relying on Report Link for those users, open the report with &ifv=1 (iframe view), and embed that URL in a Webpage widget or a simple code page instead.

This guide walks through what each piece of the toolbar actually is, which role settings remove Grid Edit and Email, how to build an ifv=1 report pane, and how to tighten the report itself so even a determined user cannot do much if they reach the full view.

What that toolbar is doing

When you drop a Report Link field onto a form and set it to display the report inline, Quickbase renders a small actions bar above the rows. Typical items:

• Full Report — opens the same report as a normal Quickbase report page (with the full page chrome).
• Grid Edit — switches the embedded rows into grid-edit mode, if the role is allowed to edit multiple records.
• Email — opens the email / share options for the report.
• More — extra report actions (print, copy, notifications setup, and similar items depending on the app and role).

On a locked-down iForms-style screen you usually want none of those. Users should see the data and nothing else. Roles can take some of the tools away. They do not reliably remove Full Report from a Report Link embed, which is why the rest of this guide focuses on a different embedding path.

Step 1: Tighten the role's User Interface settings

Start with the role that iForms (or your external / read-only users) land in. Even if you later embed with ifv=1, these settings matter for anyone who can still reach the table.

1. Open the app → Users → Roles, and open the role.
2. Go to the User Interface tab.
3. For the table that owns the report, check Hide Multi-record Options. That removes Grid Edit (and related multi-record actions) for the role.
4. In the same table row, check Hide Email Button/Links. That removes the Email link on the page bar and the email / notification items under More on reports and embedded reports.
5. Optionally check Hide UI for creating and customizing reports so the role cannot build or customize reports. If you turn that on, also clear the role's ability to save common reports so users cannot create reports they can never edit.
6. Save the role.

Confirm the table's Permissions tab for that role is view-only (or whatever narrow combination you need). If the role can still edit fields, Grid Edit may be gone but single-record edit links can still appear elsewhere.

After this step, Grid Edit and Email should disappear for that role on reports. Full Report on a Report Link embed is the one that usually remains — move on to the next step for that.

Step 2: Build the report URL with ifv=1

ifv=1 is the long-standing Quickbase URL parameter for iframe view. It strips the normal Quickbase page chrome (headers, table bar, branding, and most navigation) so the page is suitable to drop into an iframe or Webpage widget.

Open the report you want users to see, copy its URL from the browser, and append &ifv=1. The shape looks like this:

https://yourrealm.quickbase.com/db/DBID?a=q&qid=REPORTID&ifv=1

Pieces:

• DBID — the table's dbid (the part after /db/ in any table URL).
• a=q — run a report.
• qid=REPORTID — the report's numeric id (visible in the URL when you open the report).
• ifv=1 — strip the normal page chrome.

Example with placeholders filled in:

https://yourrealm.quickbase.com/db/bxxxxxxx?a=q&qid=6&ifv=1

Paste that URL into a private browser window (or an incognito session signed in as a test user in the locked-down role) to confirm you see the rows without the usual Quickbase header and table bar. That is the pane you will embed.

A few notes on ifv:

• People use ifv=1 by convention. The value is effectively a margin in pixels around the content, so ifv=0 looks almost the same and larger values add more white space.
• ifv is a practical embedding aid, not a documented "security mode." Pair it with role permissions; do not treat the stripped chrome as your only lock.
• On some forms and add/edit screens ifv can also hide Save buttons. For a report URL (a=q) that is usually what you want.

Step 3: Embed the ifv URL instead of a Report Link

This is the piece that actually gets rid of Full Report for the locked-down experience. Stop putting a Report Link on the form for these users, and put the ifv=1 URL in one of these places instead.

Option A: Webpage widget on a homepage or dashboard

1. Open the page those users land on (often a dedicated homepage or dashboard for the iForms role).
2. Add a Webpage widget (sometimes labeled as an embedded web page).
3. Paste the full report URL ending in &ifv=1.
4. Size the widget tall enough for the rows you expect, then save.

Viewers in that role see the report rows in a clean pane. They do not get the Report Link actions bar, because you never rendered a Report Link.

If the realm blocks embedding Quickbase pages in iframes, ask a realm admin to allow it (or ask Quickbase support to check the realm setting). Cross-app embeds also require the viewer to have access to the source app.

Option B: Simple code page with an iframe

If you need the pane on a code page (or you want more control over height and layout):

1. Create a Code page in the app.
2. Put an iframe that points at the same ifv=1 URL:

<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8" />
  <title>Orders for review</title>
  <style>
    html, body { margin: 0; height: 100%; }
    iframe { border: 0; width: 100%; height: 100vh; }
  </style>
</head>
<body>
  <iframe
    src="https://yourrealm.quickbase.com/db/bxxxxxxx?a=q&qid=6&ifv=1"
    title="Orders for review">
  </iframe>
</body>
</html>

3. Link users (or iForms) to that code page instead of to a form that embeds a Report Link.

Same idea as the Webpage widget: the report runs in iframe view, so the normal page chrome is already gone.

Step 4: Make the report itself tight

Even with roles and ifv=1, treat the report as something a curious user might still open in a new tab. Keep it narrow:

• Columns — only the fields those users need. Leave out internal IDs, cost fields, or anything that invites curiosity.
• Filters — bake the audience filter into the report (for example, Status is Open, or Assigned To is the current user) so the pane never shows the whole table.
• Summary reports — turn off drill-down if users should not open the underlying records from the summary.
• Sorting and grouping — set them on the report so users do not need the More menu to make sense of the data.
• Report access — on the role's User Interface tab, use Set report access so the role only sees the reports you intend, not every common report in the table.

If someone does reach the full report URL without ifv=1, view-only permissions and a tight column list still limit the damage.

What not to do

Older community answers sometimes suggested injecting JavaScript to find the toolbar element and set display: none (or remove it from the DOM). That used to work on a given form layout. It is not supported, it breaks whenever Quickbase changes the form markup, and it is easy for anyone who can open the browser console to reverse. Prefer roles plus ifv=1.

Also do not expect a Report Link field option labeled "hide Full Report." As of this writing that option does not exist, which is why the Webpage widget / code page path is the practical answer for locked-down views.

Checklist

Use this when you convert an iForms-style screen away from a noisy Report Link embed:

1. Role → User Interface → Hide Multi-record Options on the table (removes Grid Edit).
2. Role → User Interface → Hide Email Button/Links on the table (removes Email / related More items).
3. Role → Permissions → view-only (or the narrowest rights that still work).
4. Optional: Hide UI for creating and customizing reports, and clear common-report save rights for that role.
5. Copy the report URL and append &ifv=1.
6. Embed that URL in a Webpage widget or a code-page iframe — not a Report Link on the form.
7. Tighten the report: few columns, baked-in filters, no drill-down on summaries, limited report access.
8. Test as a user in the locked-down role (or an iForms session) and confirm the actions bar is gone and the rows still load.

That combination — role UI hides for Grid Edit and Email, plus an ifv=1 embed instead of Report Link — is the supported way to give people a read-only report pane without the Full Report / Grid Edit / Email / More clutter on top.