Team logins: give your developer their own sign-in
You can now invite up to four people to your HonkIO account, each with their own login and a role: Admin, Developer, Billing or Read-only. No more sharing your password.
Until today a HonkIO account had one login. If a developer, a bookkeeper or a colleague needed the dashboard, the only way in was your password. Customers asked for something better, and it is live now: each person gets their own login, with a role that decides what they can do.
Inviting someone
- Sign in and open Settings, then Team
- Click Invite someone, enter their email and pick a role
- Confirm with your password
They get an email with a link that works for 7 days. They choose their own name and password, accept the terms, and sign in to your account with their own login. An account can have up to 5 logins, yours included, at no extra cost.
Five roles
- Owner: you. Everything, including the team itself
- Admin: almost everything you can do, including billing and phone numbers, but not legal acts or managing the team
- Developer: sending, contacts, lists, templates, API keys and webhooks. Can view phone numbers but not buy them, and cannot see billing
- Billing: the balance, top-ups, auto top-up, invoices and insights. No message logs or contacts
- Read-only: can look at almost everything and change nothing
A few things stay with the owner whatever the role: submitting a business or toll-free verification, asking for higher limits, accepting the data processing agreement, changing the account email and managing the team. You can change someone's role or remove them at any time from the same page.
Keys stay inside the role
An API key, or an AI assistant connection such as Claude, can never do more than the person who created it. A Developer who connects Claude gets sending, contacts and the rest of their role, and the consent screen shows what was left out, such as buying numbers. The API keys page shows who created each key.
When someone leaves
Remove them from the Team page and they are signed out right away, and the AI assistant connections they approved stop working. API keys they created stay active, because your integration may run on one of them, and the removal dialog lists those keys so you can review and revoke them. If they had set up auto top-up with their own card, it is turned off and you get an email.
Their name and email are deleted 90 days after they are removed.
Emails go to the right person
Account emails now follow the roles. Billing emails reach the owner, admins and anyone with the Billing role. Operational emails, such as a suspended number or a delivery problem, reach everyone who works on the account except Billing and Read-only. Emails about verifications and limit requests stay with the owner, and a password reset only ever goes to the person it belongs to.
For developers
Nothing changes for keys you already have. A key created by a team member is held to that member's role: an owner-only request made with it answers 403 ROLE_FORBIDDEN, listed on the errors page. Each key in the account document now carries created_by, with the id and name of the person who made it, or null for keys made before team logins.
HonkIO