The client portal: what your client sees

The client portal is a separate, read-only site for the people at your client. Each contact you add to a workspace in External clients can open it. It shows them the state of their domains, what has been done on them and the reports you decided to share.

It is not part of the console and it is not in your menu. Each workspace has its own portal address, and it goes in the emails the contact receives. How contacts are added, what emails they get and how access is removed is in External clients.

This guide describes the portal from the contact's side: every section, what changes with their profile, and what never reaches them.

• Answer your client without opening the portal. When they call about something they see, you know which screen they are on and where that data comes from.
• Decide what to show before you invite. The domains, the profile and the reports are your choices; here you see the effect of each one.
• Know what stays inside your agency. The contact cannot change anything and does not see your console, your other clients or your subscription.
• Read the access history with sense. You know which actions of the contact leave an entry and which do not.

• The contact signs in with a code, without a password. They open the portal link from one of their emails, type their email and press Send code. A six-digit code arrives by email and is good for 10 minutes. The session lasts 24 hours; after that they ask for a new code.
• A portal belongs to one workspace. The contact sees the domains of that workspace and nothing else. The same person added to two workspaces has two separate portals, each with its own link.
• The portal is read-only. The contact can move between sections, filter and search their domains, open a report, change the language and sign out. No button there changes a domain, a setting or a contact.
• Visible domains limit everything. A contact with All workspace domains sees every domain of the workspace, including the ones you add later. A contact with Specific domains only sees only those: in the summary, in the list, in the counts and in the reports.
• The state of a domain comes from one source. If the domain is under continuous stabilization and has been measured, the portal reads its latest measurement and its open regressions. If not, it reads the last analysis from Static Analysis. The portal says which of the two it is showing, with its date.
• The portal does not claim what is not measured. A domain with no analysis is shown as not analyzed. A domain whose last measurement is too old is shown as not reviewed recently, with the date of that measurement, and nothing is said about its condition.
• The profile decides the depth. The console calls the profiles EXECUTIVE and TECHNICAL; the portal shows them to the contact as Executive and Technical. Both see the same sections, domains, scores and regressions. The Technical contact also sees the breakdown by module, the DNS records behind a regression and the technical reports.
• A report reaches the portal only when you offer it. Generating a report does not publish it. You turn on In the portal on each report, or you turn on Publish the monthly report in the portal for a domain.
• Your name and your logo are the brand of the portal. They are in the header of every screen, the sign-in card carries your name, and the foot of the page shows the year and your name. If you set them in Branding, the sign-in card also carries your portal name and your welcome message, its button takes your brand color, and the foot of every page shows your footer text and your contact email.
• The language is the contact's, and they can change it. Before signing in, the portal uses the language of their browser, or English if it is not Spanish, English or Portuguese. After signing in, it switches to the language the contact was added with. If the contact picks a language with the selector, that choice is remembered in that browser and wins from then on.
• Continuous stabilization is worded for the end client. The labels the portal uses for it are not the ones in your console. This guide describes those elements instead of quoting them.
• The portal shows the name of the workspace. The first screen greets the contact by name and says which workspace's portal they are viewing and with which profile. Give your workspaces a name your client can read.

Signing in

• Without the link of the workspace. The portal shows Invalid access and asks the contact to open the link their agency sent.
• The email step. Your logo and name at the top, a language selector, and a card with your name, a field for the email and the Send code button.
• The code step. The title Enter the code, six boxes for the code and Change email to go back. A wrong code says how many attempts are left.

The frame of every screen

• The header. Your logo and your name. On the right, the language selector (ES, EN, PT) and a round button with the first letter of the contact's email; it opens a menu with their email and Log out.
• The menu on the left. Three sections: Overview, Domains and Documents. Collapse, at the bottom, reduces it to icons.

Overview

A greeting with the contact's name, the name of the workspace and their profile. Then four blocks:

• Attention now. A headline with a colored dot that sums up all their domains: Some domains need your attention, Some domains should be reviewed, Your domains are in good overall condition or All clear. Under it, how many domains are in that situation out of the total. Then up to five domains that need attention, the most serious first, each with the reason in plain language and View detail. If there are more, a link opens the list of domains already filtered.
• What we did in the last 30 days. The facts of continuous stabilization in that period, and only those that happened: improvements protected, checks made, regressions detected and regressions recovered. With none, one line says there was no activity in the period.
• Coverage. How many of the contact's domains are under continuous stabilization out of the total, and how many have no recent analysis or no analysis at all. View domains opens the list.
• Recent activity. The latest events of continuous stabilization on their domains, up to eight rows: when it started on a domain, an improvement protected, a regression detected and a regression recovered. Events of the same kind on the same domain and day are one row with a count. Each row opens its domain.

If the contact has no domain to see, the blocks are replaced by No visible domains yet.

Domains

• The filters. All, Need attention, the domains under continuous stabilization and Not reviewed recently, each with its count. Next to them, a search box by domain name.
• The table. One row per domain, the ones that need a look first. The columns are Domain, Status, Score, a column that says whether continuous stabilization is active on the domain, and Detail.
• Status is one of six, with a colored dot: Has problems and Needs attention in red, Stable, with open points in yellow, Stable in green, Not reviewed recently in amber and Not analyzed in grey.
• Detail shows the open regressions if there are any; otherwise the improvements protected, or how long ago the domain was measured.

A click on a row opens the detail of the domain.

The detail of a domain

• The top card. The name of the domain, the date of the data shown and a mark with the profile: Executive view or Technical view. Then a headline and a short text that explains it: for an Executive contact, the state of the domain; for a Technical one, how many modules are failing or have warnings. Then the score out of 100 in a circle, with the risk level and the change since the first measurement. If the domain is under continuous stabilization, a notice says the agency follows it continuously and, if there are any, how many alerts are open.
• What needs attention now. It only appears with something open. One card per open regression: what changed, what it may affect, the module, the date it was detected or came back, the protected state and the current one, and the line The agency is following it. A Technical contact also sees the DNS record before and now. Below, under Open points or Other open points, the names of the remaining findings.
• Care history for an Executive contact, Tracking metrics for a Technical one. Three figures: Protected improvements, Open alerts and, under continuous stabilization, Under care since with its date. Below, on a domain under continuous stabilization, a line with a dot proves it is being measured: how many checks in the last 30 days, when the latest was and when the next is due. The dot is green once there is a measurement and grey before the first one. A Technical contact also sees the latest measurement of each module.
• Recent activity. The same kind of rows as in Overview, only for this domain. It is hidden when there is none.
• Documents. The reports of this domain that you offered and this contact can see. It is hidden when there are none.
• Technical detail by module. Only for a Technical contact: each module with its state, its score and how many issues, available improvements and observations it has.

Back to portal, at the top, returns to where the contact came from.

Documents

The reports you offered and this contact can see, the most recent first. Each row names the report (Executive report, Technical report, Value report or Initial state), the domain if it is of one domain, the period it covers and the date it was generated. Open shows the PDF in another tab. With none, the screen says No documents have been shared with you yet.

• External clients
• Agency branding
• Workspace dashboard
• Domain dashboard
• Continuous stabilization
• Static analysis