HubSpot Lifecycle Stage Field Visibility

Overview

The Lifecycle Stage field is one of the most critical fields on a HubSpot contact record — it drives workflow triggers, lead qualification automations, and deal creation logic. A common issue is that users cannot see this field on their contact view, which prevents them from manually updating lifecycle stages or triggering dependent automations.

This happens because HubSpot allows each user to configure their own view, and the default card view shown to most users may not include the Lifecycle Stage field. An admin must add it to the default card to make it visible for all users.

Real example: A client contact (Miriam) was unable to trigger lead lifecycle workflows because the Lifecycle Stage field wasn't visible on her contact record view. This blocked her from manually setting contacts to SQL and initiating downstream automations. — ^[1]

Why This Happens

HubSpot has two distinct layers of property visibility:

1. Your personal view — configured per user via the gear icon on a contact record. What an admin sees may differ from what a standard user sees.
2. The default card view — the shared view most users see. This is edited separately via Settings > Contacts > Contact Properties > Edit the card.

The Lifecycle Stage field may be present in the system and visible to admins in their personal view, while still being absent from the default card that everyone else sees.

How to Fix It

Add Lifecycle Stage to the Default Card View

1. Navigate to Settings → Contacts → Contact Properties
2. Click Edit the card (this edits the default view all users see)
3. Click Add properties
4. Search for Lifecycle Stage
5. Check the box to add it
6. Drag it toward the top of the property list for easy access
7. Click Save

Once saved, the field will be visible to all users on contact records — no individual user action required.

Verify the Fix

After saving, open any contact record and confirm the Lifecycle Stage field appears in the card view. You can also ask the affected user to refresh their browser and confirm visibility on their end.

Why It Matters

The Lifecycle Stage field is a trigger point for many common HubSpot automations:

• Advancing a contact from Lead → MQL → SQL triggers enrollment in nurture workflows
• Reaching SQL status can trigger BANT qualification checks and deal creation
• Downstream notifications to sales reps depend on lifecycle stage changes

If users cannot see or edit this field, the entire lead progression pipeline stalls silently.

Related Issues

When investigating lifecycle stage visibility, also check for:

• Deactivated user errors in workflows — if workflows send notifications to a contact owner who has been deactivated, they will fail with "invalid user" errors. See ^[2] for the fix.
• BANT workflow enrollment — if no contacts are reaching the BANT workflow, confirm that the SQL lifecycle stage trigger is firing correctly upstream.

Related Articles

• ^[2]
• ^[1]