What can a team member do, and what can they NOT do?

Team members on Valid Email Checker get a pared-down version of the owner dashboard — enough to be useful for the daily verification work, but locked out of anything that touches money or programmatic access. The split is enforced in the sidebar (entire links hide for team members), in the route guards (direct URL access is blocked), and in the edge functions (a team-member token cannot call owner-only endpoints). The result is that you can hand a member their credentials without worrying about them buying credits on your card or spinning up API keys you do not see.

What team members CAN do

• Verify single emails. The same widget the owner uses on the dashboard. Each verification charges the shared credit pool.
• Run bulk uploads. Upload a CSV, watch it process, download the cleaned list. The Uploads & Results page works exactly the same as the owner view, scoped to that team member.
• Connect their own integrations. Mailchimp, HubSpot, Klaviyo, ActiveCampaign, and the other ESPs/CRMs in Integrations — each team member can connect their own credentials and run verification jobs through them.
• View their own verification history. Their personal task list, results, and download links.
• See the shared credit balance. The sidebar widget shows the same Monthly + PAYG totals the owner sees, read-only.
• Manage their own profile and security. Display name, password change, 2FA, active sessions. Self-service security only — they cannot touch other members.

What team members CANNOT do

• Purchase credits. The Buy Credits sidebar link is hidden and the page route is blocked. Only the owner moves money in.
• Generate API keys. The Developer sidebar link is hidden. See why team members cannot generate API keys for the reasoning.
• View billing or invoices. The Billing & Payments tab and the Invoices tab are hidden from the Account Settings page entirely.
• Invite other team members. Only the owner can invite. The create-team-member edge function explicitly rejects any caller whose role is team_member.
• Remove or suspend other members. No member-management visibility at all on a team-member account.
• Manage subscriptions, auto-refill, or low-balance alerts. All of these are account-level settings that only the owner can change.
• See payment methods. Saved cards are completely hidden — team members cannot view or modify any payment method on file.

The accountability layer

Even though team members share the credit pool, every action is attributed to the specific member who triggered it. Each row in Credits History carries a performed_by_user_id field. Every entry in Uploads & Results shows which member started the job. As the owner, the Team page exposes per-member usage counts so you can see at a glance who consumed what. See do team members share my credits for the accounting model in detail.

Two practical implications

• If a team member wants to use the API for a side project, they cannot — they have to ask the owner to generate a key, and that key still pulls from the shared account quota.
• If a team member burns through credits faster than expected, the owner sees it immediately in Credits History filtered by that member's user ID.