Bring clients, developers, contractors and accountants onto your hosting, each with their own account and exactly the access they need. Connect a whole agency in one step.
A client connects your whole agency in one step. Everyone at your agency works on that client under their own account, with their own audit trail, and the client keeps the switch.
They enter your agency’s email on their team page, tick the roles you should have, and send it. One invite, not one per person.
The invitation binds to your agency team. Everyone on it who holds a role gets their own access to that client, under their own login.
Edit the roles, narrow the site list, or disconnect entirely. Access changes on the agency’s very next page load, and you get an email when it does.
Each person gets the overlap between what the client granted and what they can already do at the agency. The full rules, with worked examples →
Pick a role at invite time and change it whenever you like. Roles are additive, so someone can hold more than one.
Full access to sites, billing, and team management. Ownership can be transferred to another member.
You, or whoever holds the account
Full team and site management, including deleting sites. No billing access.
Your lead developer, your ops person
Can see all sites and create new ones. Cannot delete sites or manage the team.
Your in-house designers and developers
Billing access only, no site access at all. Only the team owner can grant or remove it.
A bookkeeper, an accounts inbox, a finance manager
Access to specific granted sites only. Nothing is visible until you tick the sites they should see.
A contractor, a client, a one-project freelancer
Collaborators start with nothing. You tick the sites they should reach, and those are the only sites that appear for them: not your other clients, not your billing, not your team list. Untick a site and it disappears from their account immediately.
It is the difference between trusting a freelancer with everything and hiring one for one job. Owners and Team Members still see every site on the team automatically, so this stays out of the way for your own staff.
Every team and every site keeps an Activity Log: what changed, when, and who did it. Restores, PHP bumps, plugin toggles, cache purges, team changes. When the work came through an agency connection, the client's log names the agency and the agency's own log names the person.
That is the part shared logins can never give you, and the part clients ask for first after something goes wrong.
No. Wordify bills per site, not per seat, so your team size never changes your invoice.
It lets a client give your whole agency team access in one step, instead of adding each of your staff individually. Everyone at your agency then works on that client under their own login, with their own audit trail. It is available to every Wordify team.
No. Their Activity Log records your agency’s name against agency actions. Your own team’s view shows the individual behind each one, so you keep the internal detail without exposing your staff list.
Either side can disconnect. Access ends on the next page load and nothing lingers in the client’s member list, because agency access is never copied into it. Per-person site grants under that connection end with it automatically.
Yes. That is what the Collaborator role is for. They see only the sites you tick, and nothing else on the team, including billing.
Yes. The Billing role is invoices and payment details only, with no site access at all. Only the team owner can grant or remove it.
Yes. Turn on the 2FA requirement in your team settings and every member, including anyone reaching your sites through an agency connection, must have 2FA enabled before they can touch team resources.
Yes. A team can connect several agencies, each with its own roles and site list, and each disconnected independently.
Teams, per-site access and Agency Access are available to every Wordify team. You are billed per site, never per seat, so bring as many people as the work needs.
