Checked against the product’s code on 7 November 2026.
Use Clients in your Praxis account to manage several client sites as an agency. Each client has its own organisation, sites and people. Your agency’s access comes through the client relationship and the agency member’s role. The client keeps their own login.
Confirm the workflow on your hosted account before using it to onboard a client.
Who can manage clients
Section titled “Who can manage clients”The owner or an Admin with direct membership of the agency account can manage its clients. Access delegated from another agency does not let that person manage the client’s own clients.
Client management and billing are different permissions. An agency Admin can manage clients. The agency’s owner holds the payment authority. An agency Admin can register a paid site; only an agency owner can pay for it.
Add a client and its first site
Section titled “Add a client and its first site”After registration, the contact becomes the owner of the client’s site. Use the client’s own contact address. Do not substitute an agency teammate simply to get through onboarding.
- Sign in to your account.
- Open Clients.
- In New client, enter Client name.
- Enter Contact email.
- To register a site now, fill First site name (optional).
- If you entered a first site name, choose Plan for the first site. The list offers Free and the paid plans currently available.
- Choose Add client.
- Read the result. If you registered a site, it says whether the contact’s confirmation email was sent and whether the site is held for payment.
- On Free, building starts after the contact confirms their address. On a paid plan, it waits for the agency’s payment to be confirmed.
- For a paid site, the agency owner can follow the checkout that opens after creation or use Pay for this site on the client’s page. An Admin asks an owner to complete payment.
To continue without creating a site, choose Free and leave First site name (optional) blank. A paid plan needs a first site name. This creates the client record alone. It does not register a site or send a site verification email. If verification mail cannot be sent after a site is registered, the result says so and directs you to support.
A client’s first site uses the plan selected under Plan for the first site. The contact still confirms their address for their own account. Their email confirmation landing does not show your agency’s name.
Open the client’s workspace
Section titled “Open the client’s workspace”- Select the client in the roster. Its page shows Sites, Their people and Our team’s access.
- When the site is ready, use Open admin → beside it to enter its admin.
To open the site’s team controls instead, use Team.
This is how the client relationship gives an eligible agency teammate access to that site. The first entry creates the agency member’s delegated access when the relationship and source membership allow it. The client’s team can see Managed by with the agency’s name.
This is access under the agency relationship, rather than ownership of the client’s login. An existing direct membership on the client site keeps its own status. A disabled direct membership is not bypassed by requesting delegated access.
For the team’s role boundaries, see Trust and security.
Review and end access
Section titled “Review and end access”The client page offers Prospect, Active, Suspended and Ended statuses. Changing to Suspended or Ended requires confirmation.
Suspended blocks opening sites through the agency relationship. A separate active membership on a client’s site still works. An already open site session can continue if the site does not receive the access change.
Lowering or disabling the agency membership that granted access also revokes the access derived from it. These changes are recorded.
After that membership change, read whether sign-in on the client sites was ended. If an update failed, a session already open there can continue; another Admin on that site can turn the person off under Users in its admin. Enabling and disabling the agency member again does not retry those client sites. A copilot Undo does not restore those sign-ins; after access is restored, the person opens the client site from their account again.
Client relationship status and site hosting state are separate. Ending the relationship here does not itself terminate the client’s site or delete its content.
It also does not change who pays for the client’s sites. Settle billing for those sites separately.
Billing and client collection
Section titled “Billing and client collection”The agency is the payer for its clients’ sites. A client’s owner arranges payment with the agency. This flow does not let the client pay Amadalis directly for that site.
The client’s owner is directed to the agency for payment. Their account does not offer a payment control for the managed site.
For an existing client site:
- Open Clients.
- Select the client.
- Find Billing under Sites.
- Read the state beside the control.
- As the agency owner, use Choose a plan for a free site or Pay for this site when payment is needed.
A site held for payment has no admin to open yet. If you leave checkout without paying, it stays held and Pay for this site remains the way to finish. After payment is confirmed, review the site’s progress before using Open admin.
Client statements come from your own retail price book under your brand. Send them and collect through your own payment setup. Amadalis bills your agency wholesale for its clients’ sites.
Partner terms and ownership
Section titled “Partner terms and ownership”The partner program includes partner pricing and credits applied to the agency’s own bill. Your account, client emails and client site admin carry your brand and domain. Agree the terms and account configuration with Amadalis. Read The agency partner program for the relationship and billing model.
The Team screen marks ownership as fixed. There is no action to transfer ownership in this flow. Start with the intended client owner rather than planning to transfer a site owned by the agency later.
For an existing WordPress site, arrange migration as a service. Review Known limitations before agreeing a delivery scope.