CoreInto client guide
Every page your clients see in the CoreInto client area: the store, registration, dashboard, account, services, domains, invoices, support and licences.
Client area templates (Classic and Horizon)
The client area comes in two templates, chosen under General Settings, "Client area template". Both start with the same pages, features and texts; the shell around the pages differs.
Read the guideClient area layout and menus
Every page starts with a thin strip. On the left it shows the company email address and, when "Company phone" is set, the phone number.
Read the guideHome page and store
/ opens with the heading and text set on the Store tab, a domain search box and a Transfer button, then four quick links (Buy a Domain, Order Hosting, Make Payment, Get Support).
Read the guideRegistration and sign-in
/register exists when "Visitors may create an account without ordering" is on; otherwise it sends the visitor to the store, where an account is made at checkout.
Read the guideClient dashboard
/client/ greets the person by name, with the time of their last sign-in and, when invoices are unpaid, a Pay now button with the amount due.
Read the guideAccount details, users and security
/client/details is the account's profile, in cards: Billing details (the details that appear on invoices), More details (the custom fields clients may see), the Language choice when the footer language menu is available, and Emails you receive with switches.
Read the guideMy Services
/client/services (My Services) opens with three tiles (active, pending, suspended) and, when a service is suspended, a notice with a button to the unpaid invoices. The table lists product and domain, price and term, next due date, a status badge and a Manage button.
Read the guideMy Domains
/client/domains (My Domains) opens with tiles for active domains, domains expiring within 30 days and pending ones, and a notice when something expires soon.
Read the guideInvoices, payments and credit
/client/invoices (My Invoices) opens with three tiles: unpaid invoices with the amount due, overdue ones, and what was paid this year.
Read the guideTickets, knowledgebase and announcements
/client/tickets opens with tiles for open tickets, tickets awaiting the client's reply and closed ones, and a notice when replies are waiting. The table lists subject and number, department, last update and a status badge; Open shows those not closed, All shows every ticket.
Read the guideAffiliate programme
/client/affiliates appears in the account menu when the affiliate programme is on (General Settings, Affiliates). A client who has not joined sees the commission rate, the sign-up bonus when there is one, and Join the affiliate programme. A member sees:
Read the guideLicence keys
Licence products (Licensing Manager) show their licence on the service page (see Services): the key, its status, what it is bound to and the last check. Reissue Licence clears the binding so the software can be moved; the licence binds again at its next check-in.
Read the guideContact form
/contact (Contact Us) exists when "Show the contact form" is on. The form on the left asks for a name, email address, subject and message, and a captcha when set; a signed-in person's name and address are filled in, and they are reminded that a support ticket is faster.
Read the guideChoosing a language
When more than one language is installed and "Clients may choose their language" is on, the footer of every public and client page has a language menu. The choice is kept in the browser for a year; for a signed-in person it is also saved on their account, so it follows them to another browser.
Read the guide
Frequently asked questions
Who is the CoreInto Client guide for?
Every page your clients see in the CoreInto client area: the store, registration, dashboard, account, services, domains, invoices, support and licences. Each article lists the exact menu path in the panel and the steps to follow.
Can I ask a question instead of reading?
Yes. The Help button at the bottom right of every page on this site searches this documentation and answers from the guide you pick: administrators, clients and developers each get the articles written for what they do.