Can team members trigger auto-refill on the owner's card?

On Valid Email Checker team accounts, auto-refill is owner-only territory. Team members invited to the account can verify emails, run bulk uploads, hit the API, and consume credits from the shared pool — and that consumption can absolutely push the balance below the threshold and trigger an auto-refill that charges the owner card. But the team member cannot turn auto-refill on, off, or change its settings. The toggle in the dashboard header is hidden from team-member sessions entirely.

What team members can and cannot do

Why we hide the toggle from team members

Auto-refill is a payment-method decision. Whoever can flip the toggle is, in effect, authorizing background charges against a payment method. On a team account, that payment method belongs to the owner — not the team member. Letting team members flip the toggle would mean letting one person authorize spend on another person's card without that person ever clicking anything. We avoid that whole class of problem by making auto-refill an owner-only feature.

How a team-member action can still trigger a refill

If the owner has auto-refill on, anything the team member does that drains the shared credit balance below the threshold will cause the owner's card to be charged the next time the monitoring tick runs. So the indirect effect is real — a team member running a 10,000-row bulk job can absolutely cause an auto-refill on the owner's card. What the team member cannot do is change the parameters of that charge: the amount, the timing, the monthly cap. Those are locked to whatever the owner configured.

What the owner sees, what the team member sees

• When a refill fires, the owner gets the in-app notification and the email. The team member who triggered the consumption does not get an email — they would not necessarily know what payment instrument was charged.
• The owner sees the refill in the Auto-Refill History page (linked to their account). Team members do not have access to that page.
• The owner sees the corresponding row in Credits History with transaction_type = auto_refill. Team members can see Credits History but the financial detail (the charged card, the invoice) is not exposed.

If the team needs more control

If your team needs different people authorized to manage auto-refill, the solution is to have those people be co-owners on the account, not just invited team members. Multi-owner accounts are not a standard feature today but can be set up by request for enterprise plans — contact support with your requirements. Each co-owner would have their own card on file and their own permission to manage the auto-refill toggle, but only one card can be the active billing card at a time.

A common scenario worth knowing

A team member kicks off a large bulk upload at 4:55 PM on Friday and leaves for the weekend. The job drains the credit balance below the threshold around 5:10 PM. Auto-refill, configured by the owner on Balanced timing, fires at 5:15 PM and charges the owner card. The owner sees the notification email Friday evening and confirms everything is fine, the team member returns Monday with the job finished, no stall and no surprise. This is exactly the workflow auto-refill is designed for — but it only works because the owner authorized the safety net up front. Team members cannot opt themselves into it.