Quick Answer
When a new HubSpot user logs in and sees an empty portal — no contacts, no deals, empty dashboards — the data is almost never missing. The usual causes are record access permissions set to "owned only" or "team only" while the user owns nothing yet, a saved view with filters that exclude everything, dashboards that were never shared with the user, or a pipeline the user has no access to. Start with the user's object permissions in Settings, then check which view and filters they are looking at, then check sharing on the dashboards they expected to see. This is the exact sequence Vantage Point's HubSpot team runs during onboarding engagements.
Key Takeaways (TL;DR)
- Empty portal ≠ empty CRM. The records exist; the user's permissions or view is hiding them. Check access before assuming an import failed.
- Most common cause: record access set to "owned only" or "team only" for a user who owns nothing and belongs to no team.
- Most overlooked cause: the saved view itself — a filter on owner, pipeline, or date range can make a healthy pipeline look empty.
- Dashboards and reports are shared separately from record access — a user can see deals and still see no dashboards.
- Admins can set default views for new users so nobody lands on a blank index page again.
Why a New User's Portal Looks Empty
HubSpot is deliberately conservative about who sees what. Out of the box, a freshly created user can have object access limited to records they own, no team membership, no shared dashboards, and an index page whose default view was configured for someone else's workflow. Every one of those settings is invisible to the new user — they just see a blank screen and assume the data was never migrated or the portal is broken.
For the admin, the debugging job is to work from the inside out: what is this user allowed to see, what are they currently looking at, and what has actually been shared with them. The sections below walk through each cause in the order you should check them.
Cause 1: Record Access Permissions Are Too Narrow
In HubSpot, object permissions control whether a user can view, edit, or delete contacts, companies, deals, and tickets — and each can be scoped to everything, team only, or owned only. A sales rep scoped to "owned only" who has not been assigned a single record will see an empty CRM that is actually full.
To check, go to Settings → Users & Teams, open the user, and review the CRM object permissions. If the scope is owned or team only, either broaden the access or — more commonly — assign records to the user and make sure they belong to the right team. Team scoping fails silently when the user was never added to a team, or when records are owned by people outside their team. If you are still designing your seat and permission model, our guide to HubSpot seat types and view-only access covers the license side of this decision.
Cause 2: The View or Filters Are Hiding Everything
Even users with full record access can land on an index page that shows nothing. The culprit is usually the saved view: a filter on record owner, pipeline, lifecycle stage, or creation date that matches zero records for this user. The classic version is a rep whose deals index defaults to a view filtered to a pipeline they do not work in.
Have the user click the view tabs and switch to a standard "All records" view, or reset the filters in the current view. If the same wrong default keeps appearing for every new hire, fix it at the source: admins with the right permissions can define account-wide default view tabs for each object under Settings → Data Management → Objects → Index Customization. HubSpot applies those defaults to new users and to anyone who has not customized their own tabs — so one good configuration ends this entire category of ticket.
Cause 3: Dashboards and Reports Were Never Shared
Dashboard access is independent of record access. A user can be able to view every deal in the portal and still open the dashboards menu to find nothing, because each dashboard has its own sharing setting — private to the owner, shared with specific teams, or visible to everyone. New users typically see only dashboards explicitly shared with them or their team.
Open the dashboard in question, check its sharing settings, and add the user or their team. Do the same for any saved reports they need. If the team relies on a standard set of dashboards, make "share the core dashboards with the team" a step in your onboarding checklist rather than a reactive fix.
Cause 4: Pipeline, Inbox, or Tool Access
Some emptiness is feature-level rather than record-level. A user without access to a specific deal pipeline sees other pipelines but not the one they expected. A rep without conversations inbox access sees no shared inbox. A user without marketing email access sees no email tools at all. Each of these is a separate permission or seat assignment, and each produces the same "it's empty" complaint from the user's side.
When the report is "I can't see X," translate it into "which permission governs X" before changing anything. HubSpot's user permissions guide lists every tool-level toggle; the broader patterns — sync errors, workflow failures, and the permission architecture underneath — are covered in our HubSpot admin troubleshooting guide.
How Should Admins Troubleshoot This, Step by Step?
1. Reproduce it as the user
Log in as the user (or have them share their screen) and note exactly which pages are empty — index pages, dashboards, a specific pipeline, or an entire tool. "Empty deals" and "empty everything" point at different causes.
2. Check object permissions first
In Settings → Users & Teams, confirm the user has view access to the relevant objects and note the scope. If it is "owned only," check how many records they actually own — the fastest test is filtering the object's index page by owner as an admin.
3. Check team membership
If access is team-scoped, confirm the user is on the right team and that the records they expect are owned by teammates. A user on no team with team-only access sees nothing.
4. Inspect the view, not just the data
Open the same index page as the user and read the active filters. Remove filters one at a time until records appear; the last removed filter is your culprit. Then decide whether the fix is the user's view or the account-wide default.
5. Verify sharing on dashboards, reports, and pipelines
Check the sharing settings on every asset the user expected. Add the user or team, and document the sharing model so the next new hire does not generate the same ticket.
6. Set defaults so it never happens again
Use the Index Customization settings to define default view tabs per object, standardize dashboard sharing by team, and write the permission assignments into your onboarding runbook. An empty portal is a configuration problem, and configuration problems are preventable.
How Vantage Point Helps
Permission and visibility problems are rarely one-off fixes — they are symptoms of a permission model that was never designed. We help teams audit HubSpot user roles, build team- and pipeline-based access, configure default views and dashboard sharing, and document the whole model so onboarding stops generating tickets. Our managed services team can own this as an ongoing function if your admin capacity is stretched.
New Hires Staring at an Empty HubSpot Portal?
We will audit your permission model, fix the immediate visibility problems, and set the defaults that keep every future new user productive on day one.
Frequently Asked Questions
Why does a new HubSpot user see no contacts, deals, or tickets?
Almost always a permissions scope issue. If the user's object access is set to "owned only" or "team only" and they own no records or belong to no team, the index pages render empty even though the data exists. Check Settings → Users & Teams → the user's CRM object permissions before investigating anything else.
Can a saved view make a HubSpot pipeline look empty?
Yes. Saved views carry filters for owner, pipeline, stage, date ranges, and more. A user whose default view filters to the wrong pipeline or a restrictive owner filter will see zero records with full permissions in place. Switching to the standard "All" view or clearing filters is the fastest test.
Why can a user see deals but no dashboards?
Dashboards and reports have their own sharing settings, separate from record permissions. Each dashboard can be private, team-shared, or visible to everyone. A new user sees only what has been explicitly shared with them or their team — open the dashboard's sharing settings and add them.
How do we set a default view for every new HubSpot user?
Admins with Super Admin permissions can configure account-wide default view tabs under Settings → Data Management → Objects → Index Customization. HubSpot applies these defaults to new users and to anyone who has not customized their own tabs. Users can still change their own tabs afterward, which overrides the default for them only.
What is the difference between "team only" and "owned only" access?
"Owned only" limits a user to records assigned to them personally. "Team only" extends visibility to records owned by anyone on their HubSpot team. Both produce empty screens when misconfigured: "owned only" fails when nothing is assigned yet, and "team only" fails when the user was never added to a team.
Should every new user get full record access?
Not necessarily — scoped access is often the right design for sales teams. The fix for an empty portal is usually to assign records and teams correctly, not to widen permissions. Grant broader access only when the role genuinely requires it, and document the decision in your permission model.
Sources
- HubSpot Knowledge Base: User Permissions Guide
- HubSpot Knowledge Base: Manage Saved and Default Index Page Views
- HubSpot Knowledge Base: Limit Access to Your HubSpot Assets
Vantage Point is a boutique CRM consulting firm helping businesses transform with Salesforce, HubSpot, and AI. Learn more at vantagepoint.io.
