User Permissions: Why a User Cannot See the QBO Bank Feed

When a user cannot see the Bank transactions screen or a specific bank feed in QuickBooks Online, the issue is almost always caused by role-based permission restrictions, limited custom roles, or navigation caching errors. QuickBooks Online strictly controls financial access: users assigned to standard “Customers only” or “Vendors only” roles are prevented from viewing banking menus to protect sensitive cash balances. To restore bank feed access, a Primary Admin or Company Admin must update the user’s assigned role in Manage Users to grant “All” access, or enable specific “Banking” permissions in QuickBooks Online Advanced.

Fast-Fix: The 45-Second Solution

To give a user access to the bank feed, sign in as a Primary Admin or Company Admin, click the Gear icon, and select Manage users. Locate the user, click Edit, and change their role from limited access (like “Standard – Customers only”) to “Standard – All access” or “Company Admin.” In QuickBooks Online Advanced, edit the user’s Custom Role, expand the “Banking” category, toggle on “Bank transactions” view and edit permissions, then save.


Quick Status & Triage Snapshot

Diagnostic MetricAssessment
Data Risk TierZero Risk: Adjusting user permissions does not alter, delete, or overwrite any general ledger transactions.
Multi-User ImpactIndividual: Only affects the specific user whose role profile is being modified.
Common TriggerRole changes, hiring transitions, onboarding an internal bookkeeper under a sales-only role, or recent tier migrations.
Estimated Fix Time2 to 5 minutes.

Diagnostic Flowchart: Bank Feed Visibility Decision Path

[User Cannot See Bank Feed or Banking Menu]
                     │
                     ▼
What subscription tier is the company file running?
     │
     ├─► SIMPLE START / ESSENTIALS / PLUS
     │     │
     │     ▼
     │   What role is the user currently assigned in "Manage users"?
     │     ├─► "Customers only" or "Vendors only" ──► Cannot access Banking (By Design)
     │     │                                           └─► Action: Change role to "All access"
     │     └─► "All access" or "Company Admin"
     │            └─► Check browser menu view (Menu Bookmarks / Navigation customization)
     │
     └─► ADVANCED
           │
           ▼
         Is the user assigned a "Custom Role"?
           ├─► YES ──► Check Custom Role settings ──► Ensure "Banking" toggle is checked
           └─► NO  ──► Verify user is not set to "Time tracking" or "Reports only"

Technical Anatomy: Role Architecture and Banking Security

QuickBooks Online protects cash balances and transaction logs by tying menu rendering directly to database access control lists (ACLs). When a user signs in, the interface only builds navigation links for modules that the user has clearance to query:

  1. Standard Role Limitations (Simple Start, Essentials, Plus): Pre-set roles are broad. If an employee is set to “Standard – Customers,” QuickBooks restricts all access to general ledger bank accounts, the Chart of Accounts, and the Transactions > Bank transactions tab to keep company cash balances confidential.
  2. Custom Roles (QuickBooks Online Advanced): Administrators can selectively grant or withhold permissions. If the “Banking” module permissions are not explicitly checked when building a custom role, the entire banking sub-menu is hidden from the sidebar.
  3. Menu View Layouts (Business View vs. Accountant View): Sometimes a user has permission, but navigation customization or bookmarking changes have moved the bank feed. In “Business View,” the feed is located under Bookkeeping > Transactions > Bank transactions, whereas in “Accountant View,” it sits under Transactions > Bank transactions.

If you are trying to add an external professional rather than an internal employee, do not burn a billable user seat. Review Accountant Access: What to Do When an Invited User Can’t Access Books.


Is Your Data at Risk?

Modifying a user’s permissions carries zero risk to your financial data.

  • Existing Feed Data: The bank feed itself, rules, and pending items in the “For Review” tab are unchanged when editing user profiles.
  • Audit Trail Safety: QuickBooks logs all permission adjustments in the Audit Log, recording which admin granted access and when.
  • Precaution: Only grant bank feed access to trusted personnel. Users who can view the bank feed can see current bank balances, view sensitive vendor disbursements, and categorize or match expenditures directly into your permanent ledger.

Step-by-Step Repair Guide

Step 1: Verify the User’s Current Role (Admin Action)

Only a Primary Admin or Company Admin can manage roles:

  1. Sign in to QuickBooks Online with your administrative login.
  2. Click the Gear icon in the top-right header and select Manage users.
  3. Locate the affected employee in the user list.
  4. Check the Role column:
    • If it reads Standard user (Customers only) or Standard user (Vendors only), they cannot see bank transactions.
    • If it reads Reports only or Time tracking only, all transaction screens are hidden.
  • If it reads Standard user (Customers only) or Standard user (Vendors only), they cannot see bank transactions.
  • If it reads Reports only or Time tracking only, all transaction screens are hidden.

If your subscription blocks you from adjusting user seats due to license caps, review User Limit Reached: How to Audit and Remove Inactive QBO Users.

Step 2: Update Standard Roles (Essentials and Plus)

  1. In the Manage users table, locate the user and click Edit in the Action column.
  2. Under the User type or Role selection, change their status to Standard user.
  3. Under access rights, select All (which provides access to Customers, Vendors, and Banking).
  4. Choose whether they have rights to add/edit users or manage subscription details (typically set to No for non-executive staff).
  5. Click Save.
  6. Have the user log out of QuickBooks Online completely and log back in to reload their navigation menu.

Step 3: Configure Custom Role Permissions (QuickBooks Online Advanced)

If your company runs QuickBooks Online Advanced:

  1. Go to Gear icon > Manage users.
  2. Click the Roles tab at the top of the screen.
  3. Locate the custom role assigned to the user and click Edit.
  4. Scroll down to the Banking permission section.
  5. Check the box for Banking, then ensure View, Create, and Edit permissions are selected for Bank transactions.
  6. If you want the user to review entries without editing the Chart of Accounts, leave account registers unchecked while keeping the bank feed checked.
  7. Click Save role. The user’s interface will update within seconds.

Step 4: Fix Menu Customization and Browser Cache Glitches

If the user’s role is confirmed as “Company Admin” or “Standard – All access,” but the menu remains missing on their screen:

  1. Have the user look at their left-hand sidebar menu.
  2. Click Bookmarks > Pencil icon (Edit bookmarks).
  3. Look for Bank transactions under the available menu items and check its bookmark box. Click Save.
  4. If the menu still does not render, have the user launch an Incognito window and sign in at qbo.intuit.com.
  5. If the banking tab appears in Incognito mode, the user’s primary browser holds stale interface assets. Have them clear their Intuit browser cache: Cache & Cookies: How to Clear Browser Data Specifically for Intuit.

If the user is assigned to multiple companies and sees the feed in one entity but not another, verify they are switched into the correct company file using Switching Companies: How to Navigate Between Multiple QBO Accounts.


Hard Stop: When Bank Accounts Within the Feed Are Missing

If a user can access the Bank transactions screen, but one specific bank card or credit card tile is missing from the top row:


Closing the Books

Bank feed visibility is governed entirely by user permissions. By verifying that your team members have “All access” or an enabled “Banking” role in QuickBooks Advanced, you can ensure they have the tools they need to review transactions without compromising your company’s broader administrative security.