Enrollment links: What they are and how to add them

When an employee accepts their ICHRA health benefits, they'll need to enroll in a qualifying individual health plan. If you choose to be the Agent of Record, the Enrollment Links you enter tell the portal where to send them, based on their state.

Depending on the state, that may be:

  • A HealthSherpa shopping link (your agency's links or StretchDollar's if you prefer that we're the AOR)
  • A state-based marketplace (for example, Covered California or Pennie)
  • Another carrier or enrollment URL your agency uses in that state
  1. Log in at dashboard.stretchdollar.com
  2. In the left sidebar, open Enrollment Links & States
  3. For each state you need to configure:
    • Paste the enrollment URL for that state into the link field, or
    • Enter your HealthSherpa agent ID (if shown) so the portal can generate the correct shopping link
  4. Confirm the URL looks complete (it should start with https://     )
  5. Save your changes

URL validation runs as you edit. If a link is invalid, fix the error before saving.

  1. Go to Enrollment Links & States
  2. Find the state you need to change
  3. Replace the URL (or update the agent ID, if you're regenerating a HealthSherpa link)
  4. Save your changes

Update links when a marketplace URL changes, you add a newly licensed BOR state, or your agency gets a new HealthSherpa agent ID / carrier enrollment URL.

FAQ

Only Organization Admins can add or update enrollment links.


What happens if I leave a state blank?

If no enrollment link is added, employees in that state will be directed to StretchDollar's default shopping experience instead.


No. Your organization is responsible for keeping enrollment links current.


Is this the same as inviting employees?

No. Employer admins invite employees to begin the benefits process.

Enrollment links determine where employees are sent to shop for their individual health plan after they begin their benefits setup.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.