Can my biller use my CHAMPS login?

No — and they shouldn't. Michigan Medicaid's model is that each person creates their own MiLogin account and is granted access as an individual user. Sharing a login undermines your audit trail and creates security and compliance risk. Give access through profiles instead.

What is the Provider Domain Administrator in CHAMPS?

The Provider Domain Administrator is the user who controls access to your provider domain (NPI) in CHAMPS — deciding who can access the provider's information and which profile each user gets. The person who submitted the Provider Enrollment application usually becomes the default administrator; additional administrators require a separate approved request.

What access does a Medicaid biller need in CHAMPS?

It depends on what they do. A claims-focused biller needs the claims/encounters functions; a biller who verifies benefits needs eligibility access; a biller who handles authorizations needs prior authorization access; and a biller who updates enrollment needs an enrollment profile. Grant only what the work requires, and verify the exact current profile names in your Admin tab.

How do I give CHAMPS Claims Access?

Your Domain Administrator adds the biller on the Admin tab — by the biller's own MiLogin ID — and assigns a claims-capable profile (such as Claims Access, or a broader profile that includes claims). The biller must already have a MiLogin account and have requested the CHAMPS application. Confirm the current profile names and steps in your live CHAMPS environment before assigning.

What if my old biller or admin still has access?

Your Domain Administrator can remove a departed user's access directly on the Admin tab — no password change needed, since each user has their own login. If the person who left was your Domain Administrator and nobody else has admin rights, contact the MDHHS Provider Enrollment Unit to reset domain rights and establish a new administrator.

Can Bomi help manage Michigan Medicaid billing workflows?

Yes. Bomi helps therapy practices with eligibility checks, claims, denials, EOB review, prior authorization tracking, credentialing workflows, and payer follow-up — working within your CHAMPS access model so your Domain Administrator stays in control and no one has to share a login. We can't guarantee enrollment approval, plan contracting, or reimbursement, but we can keep the operational side running.

Billing

Credentialing

Medicaid

Michigan

Give Your Biller CHAMPS Access

By George Ruan • July 6, 2026

Last updated: July 6, 2026.

Bottom line: You give your biller access to Michigan Medicaid's CHAMPS system by having them create their own MiLogin account, then having your Provider Domain Administrator grant them the right access profile inside CHAMPS. You do not hand over your username and password. CHAMPS is built for exactly this — one Domain Administrator per provider (NPI) domain who adds each user by their MiLogin ID and assigns only the permissions that person needs: claims, eligibility checks, prior authorization, or enrollment updates. Sharing a login is unnecessary and makes it impossible to tell who did what. Here's how the access model works and how to hand off billing safely.

Sections

Why your biller needs CHAMPS access
Step one: everyone gets their own MiLogin (never share a login)
What the Provider Domain Administrator does
Common CHAMPS access profiles
Which roles a biller may actually need
What should stay with the provider or practice owner
What to prepare before you grant access
What to do if you lost admin access
Action Steps for Providers
Where Bomi Fits
Sources

Why your biller needs CHAMPS access

CHAMPS — the Community Health Automated Medicaid Processing System — is where Michigan Medicaid billing actually happens. A biller working your Medicaid revenue needs to get in and do the day-to-day work: verify member eligibility, submit and status claims, handle adjustments and voids, and work prior authorizations. All of that lives behind CHAMPS access profiles.

The instinct is to just text your biller the login. Don't. Michigan built CHAMPS so each person has their own credentials and scoped access — so you can see who did what, turn one person's access on or off without disrupting anyone else, and never rotate a shared password when your team changes.

A quick clarification: CHAMPS portal access is about who can operate the portal for your enrolled NPI. It is not the same as being enrolled, credentialed, or contracted with Michigan's Medicaid Health Plans (MHPs) or the PIHP/CMHSP behavioral health system — those are separate steps. (See our posts on Michigan Medicaid provider enrollment and Medicaid Health Plan credentialing.)

Before anyone can touch CHAMPS, they need a MiLogin account — the state's login layer and the front door to CHAMPS. MDHHS's guidance is that each user applies for their own MiLogin username and password and then subscribes to (requests) the CHAMPS application.

This is the single most important rule in this article: your biller should register their own MiLogin account, not borrow yours. A shared login defeats the entire access model, muddies your audit trail, and can create real security and compliance exposure around Medicaid data.

Here's the sequence at a high level:

The biller creates their own MiLogin account.
The biller requests access to the CHAMPS application through MiLogin.
Your Provider Domain Administrator then grants that biller the appropriate access profile inside CHAMPS.

Nobody gets useful access to your provider data just by making a MiLogin account. The Domain Administrator has to add them and assign a profile — the control point that makes this safe.

What the Provider Domain Administrator does

The Provider Domain Administrator is the person who controls access to a provider domain (your NPI) in CHAMPS. Per MDHHS, the administrator is responsible for assigning rights to all users in the organization who need the provider's information — deciding who gets in and what profile they're granted. A few things worth knowing:

The MiLogin user who submits the Provider Enrollment application typically becomes the Domain Administrator for that domain by default.
An organization can have more than one Domain Administrator, but each additional one has to be set up through a separate, approved request.
The administrator adds and removes users and profiles — so when a biller leaves, the same person can revoke access, no password change required.

In practical terms, the add-a-user flow lives on the Admin tab in CHAMPS: the administrator selects the billing NPI and the Domain Administrator profile, opens the Admin tab, goes to the user list, chooses "add," enters the new user's MiLogin ID, and checks the profiles that person should have. (Screens and labels change over time — confirm the exact current steps in your own Admin tab.)

Common CHAMPS access profiles

CHAMPS uses named access profiles so you can grant just what a user needs. As of this research, MDHHS's Domain Administrator materials describe a set of profiles that includes:

Domain Administrator — assigns and removes access for other users on the domain.
CHAMPS Full Access — broad access across the fee-for-service subsystems (typically view access to Provider Enrollment plus working access to Eligibility, Claims, and Prior Authorization).
CHAMPS Limited Access — a narrower version of the above; confirm its exact scope before assigning.
Claims Access — the Claims and Encounters area only.
Eligibility Inquiry — running member eligibility checks.
Prior Authorization Access — the Prior Authorization functions.
Provider Enrollment Access / Provider Enrollment View Access — working (or just viewing) enrollment records.
Billing Agent Access — geared toward billing-agent users.
MCO Provider Access — managed care organization functions.

Verify the current profile names and their exact scope in your live Admin tab before you assign anything. MDHHS updates CHAMPS profiles and labels periodically. Treat the list above as a map of the kinds of access that exist, confirm the specifics against what you see in CHAMPS today, and don't over-grant "just in case."

Which roles a biller may actually need

Match the profile to the work. A biller doesn't automatically need everything — and giving them the maximum profile "to be safe" is the opposite of safe.

Submits and works claims: needs the Claims and Encounters functions — Direct Data Entry (DDE), batch upload, claim status, adjustments/voids — so a claims-capable profile.
Verifies benefits: needs eligibility access to run member checks (web screens or a 270 request) — Eligibility Inquiry or a broader profile.
Manages prior authorizations: needs Prior Authorization access to submit and track PAs (each gets a tracking number in CHAMPS).
Updates enrollment records (revalidations, service locations, address changes): needs a Provider Enrollment profile — many practices keep this one closer to the owner.

One more distinction for billing agents and clearinghouses: submitting electronic transactions (like a 270 eligibility or 276 claim-status request) on your behalf can require the submitting entity to be associated in CHAMPS as your Billing Agent / Trading Partner — a separate setup from a user profile. If your biller submits through a clearinghouse or their own EDI connection, confirm whether that association is also required.

What should stay with the provider or practice owner

Some control should not leave the building. As a rule of thumb, the practice owner (or a trusted internal manager) should retain:

The Domain Administrator role itself. Whoever holds it can add and remove everyone else's access. Keep it with an owner or long-tenured staff member, and add a second internal administrator as a backup so you're never locked out if one person leaves.
Sensitive enrollment control. Decide deliberately whether an outside biller should be able to edit enrollment records or only view them.
Your MiLogin credentials. Always. Your login is yours.

You can let a biller do the heavy operational lifting on claims, eligibility, and PAs while keeping the administrator keys in-house.

What to prepare before you grant access

Gather these before you add a user and the handoff takes minutes:

Your provider domain / billing NPI — the domain the biller will work under.
The biller's MiLogin User ID — they create it and send it to you; you never need their password.
A decision on scope — which profile(s) this person should get, based on the work they'll do.
Who your current Domain Administrator is — that's the person who has to make the change.

What to do if you lost admin access

This is a common, fixable situation: the person who enrolled the practice has left, nobody transferred the Domain Administrator rights, and now no one can add your new biller.

Per MDHHS guidance, if the user who completed the Provider Enrollment application left without transferring domain rights — or you aren't sure who holds them — the MDHHS Provider Enrollment Unit can reset or grant Domain Administrator rights. The current guidance points to:

Calling Provider Enrollment at 1-800-292-2550 to have domain rights reset, and
Establishing a new Domain Administrator by submitting the required electronic-signature paperwork (the Electronic Signature Agreement Cover Sheet and Electronic Signature Agreement) to the MDHHS domain-requests mailbox.

Because this involves state paperwork and identity verification, confirm the current forms, email address, and phone number with MDHHS before you file anything — the exact document numbers and routing can change. The takeaway: a lost administrator is recoverable through a defined MDHHS process, not a reason to start sharing logins as a workaround.

Action Steps for Providers

Have your biller create their own MiLogin account and request the CHAMPS application. Do not share your credentials.
Identify your current Provider Domain Administrator. If you don't know who it is, or that person has left, start the MDHHS domain-rights recovery process now so you're not blocked later.
Decide the scope of access the biller needs — claims, eligibility, prior authorization, enrollment — and grant only those profiles.
Add the user on the Admin tab by their MiLogin ID and assign the chosen profile(s), verifying the current screens and profile names in your live CHAMPS.
If a clearinghouse or billing agent will submit electronic transactions, confirm whether a separate Billing Agent / Trading Partner association is required.
Keep the Domain Administrator role in-house, with a second internal administrator as a backup.
Review access when staff or vendors change — revoke departed users' profiles promptly; no password rotation required.

Where Bomi Fits

Handing off Michigan Medicaid billing shouldn't mean handing over your passwords — or guessing which CHAMPS profile to click. Bomi helps therapy practices map out exactly what access a biller needs, document the handoff cleanly, and keep the day-to-day work moving: eligibility checks, claims, denials, EOB review, prior authorization tracking, credentialing workflows, and payer follow-up. We work within your access model, not around it — your Domain Administrator stays in control, each user keeps their own login, and your revenue operations keep running.

Want help keeping Michigan Medicaid billing and credentialing workflows straight? Talk to Bomi about the operational handoff — we can help you scope the right CHAMPS access and manage the billing work behind it.

This post is for general operational education and is not legal, compliance, or billing advice. Always confirm current MDHHS, Medicaid Health Plan, PIHP, CMHSP, and Provider Manual requirements before submitting enrollment, claims, or authorizations.

Sources

Want Bomi to handle insurance billing?

Bomi helps therapy practices with benefit checks, claims, denials, balances, CAQH, attestations, and revenue management.

Talk to Bomi about billing