Guides and FAQ

How to install it

1. 1In Tendfolio, open Sites → Add WordPress installation and write the full address (with https://). The label fills itself in with the domain: change it only if you prefer another name. The page with the steps opens: keep it open until the end.
2. 2Download the plugin with the button in the first step: it is a .zip file, do not unpack it.
3. 3In the site’s WordPress go to Plugins → Add New Plugin → Upload Plugin, choose the .zip, press Install Now and then Activate Plugin. A Tendfolio entry appears under Settings.
4. 4Go back to Tendfolio and press Open next to the site’s address: Settings → Tendfolio opens with the key already in the field, even if WordPress asks you to log in first. Press Salva e connetti. If the field is empty, copy the key from the Tendfolio page and paste it yourself.
5. 5Nothing else to do: as soon as the connector answers, the Tendfolio page says so on its own and takes you to the site card, where the first read has already started. If you closed the page before connecting, open the site from Sites: its card shows Connect this site, with the same steps and a new key — the old one stops working.

Site states, and what they mean

• Waiting — the key was generated but the plugin has not been in touch yet. It is almost always one of two things: the key pasted half way (it is long, use the copy button) or a site that cannot be reached from the internet — local, behind a VPN or password-protected.
• Connected — all good: Tendfolio reads the site's state and, when you ask it to, writes to it (updates, backups, fixes).
• Disconnected — the site has not answered for a while. Tendfolio keeps retrying on its own, with nothing needed from you: when it becomes reachable again it reconnects. Only if the plugin was removed or reinstalled on the site, or WordPress was rebuilt, open the site card and use Reconnect it: it gives you a new key and the same steps as the first connection.
• Error — the plugin answers but something is wrong: invalid key, filesystem permissions, a PHP version that is too old. The exact message is on the site card. If the key on the site is no longer the right one, Reconnect it on the same card generates a new one.

What whoever runs the site decides

• In WordPress, Settings → Tendfolio, the section What Tendfolio can do on this site turns off one-click login as an administrator and restores, clones included. They’re on by default: turning them off is the choice of whoever runs the site.
• When they’re off, Tendfolio says so instead of trying: Open WP-Admin explains where to turn it back on, and a restore or a clone onto that site stops before touching anything.
• Updates, backups, checks and content keep working. To stop everything, the same page has Disconnect from Tendfolio: it removes the key from the site, and from then on Tendfolio can’t do anything there; backups already taken stay in Tendfolio.
• The connector installs plugins only from WordPress.org or from Tendfolio, and backups carry wp-config.php without the session keys: rebuilding a site from scratch generates new ones, and whoever was signed in signs in again. From version 3.2 it accepts an update of itself only if Tendfolio signed it with a key that isn’t on its servers: if someone took control of them, they couldn’t send sites a connector of their own. From 3.4.1 the connection secret is not included in backups, and Tendfolio can replace it remotely without disconnecting the site: it did so on every site after the 21 October 2026 incident at its server provider, and you find it in the log as “Connection secret replaced by Tendfolio”.

The site tabs

• Overview — at the top a sentence that says how the site is doing, then the four numbers (uptime, response, security, backups) and the To do queue, most urgent first: serious vulnerabilities, updates made outside Tendfolio, broken links, updates to run with Safe Update, minor notices. At the bottom the content, the visits, maintenance mode and the AI Copilot’s first suggestion.
• Security — the site’s alerts, most severe first; vulnerabilities of the same plugin share one row, which opens to show them one by one.
• Links — broken links found in the content, with where they are cited.
• Plugins — split into Active and Inactive, with installed version and available version. For each one you choose how it updates: automatic, manual or locked updates. Inactive ones can be activated again or deleted, with a confirmation on the row.
• Backup — the available copies with date and size, download and restore, plus the automatic schedule.
• Content — in three parts: the site’s posts and pages, Write with AI to generate new ones, and the AI editorial plan.
• Users — the site’s WordPress accounts, with role and posts written; from here you block whoever should no longer get in.
• Client report — the period summary to send to whoever pays, with the public link.
• Activity — everything that happened on this site, including changes someone else made directly in wp-admin.

What you can do from here

• Open WP-Admin in one click, with no shared passwords: Tendfolio opens a one-time session valid for 60 seconds. It is the right way to give a collaborator temporary access without creating them a user.
• Put the site in maintenance with a message you write. While it is in maintenance the checks continue but stay out of the statistics, so planned work does not eat into the month's availability.
• From the … menu at the top right of the header: rename the site, fix its address, download a fresh copy of the connector or update it remotely.
• Remove the site from the fleet when the relationship ends: the plugin stays installed but stops answering, and the history leaves your panel.
• Coloured labels — the client, a contract, a priority (“Rossi Ltd”, “Monthly maintenance”, “VIP”). A site can have up to 20; they also appear in the site header, and clicking one takes you to the list filtered by it.

Adding and using labels

1. 1In the sites table click the site’s labels, or + Label when you hover a row without any: a menu opens attached to the cell. The same menu opens from the button next to the labels in the site header.
2. 2Tick the labels you want: every tick saves by itself, there is nothing to confirm. To create a new one type its name in the field at the top, pick a colour from the dots and press Enter: it is created and added to the site straight away.
3. 3To filter, use the Label button in the table bar and tick one or more labels: you keep the sites that have at least one of them, and No label finds those that have none yet. The × on the button removes the filter; the filter stays in the page address, so the link can be shared.
4. 4To rename them, change their colour or delete them go to Settings › Labels (you need permission to manage the organisation): clicking a row opens name and colour, and giving a label the name of another one merges them.

How to set up monitoring for a site

1. 1Open Monitoring and pick the site, or go to its card: Settings is at the top right. The On switch next to the X pauses the checks without losing anything you set up.
2. 2Under What we check pick one of the three cards. That it responds is enough for most sites. That a text is there is for something that MUST be there — an “Add to cart” button, a phone number, a product name: type it in Text to look for and we alert you when it disappears. That a text isn’t there does the opposite, for words like “Maintenance” or “Service suspended”. Keep WordPress error pages count as down ticked.
3. 3Choose how often to check it on the interval line. One minute for sites that sell, five or ten for brochure sites: checking more often does not make them more reliable, it only shortens the gap between the failure and the alert. The free plan starts at five minutes — tighter intervals stay on the line with a lock, and the choice you made becomes valid again if you change plan.
4. 4Under When to alert you set how many failed checks in a row should raise the alarm: next to it you read how much downtime that means. With three and a one-minute interval, a site has to be unreachable for three minutes before anyone is woken up: that is the filter that keeps network hiccups out.
5. 5Below, Who to alert and how lists the people who can see the site, each with Email and Telegram: turn channels on and off person by person. A channel that can’t reach someone is off and says why — “email not confirmed”, “Telegram not linked”. With Add an email address you also alert someone outside the team, the client for example: they only get the email, without the link to the panel.
6. 6At the bottom, the Post-update check row tells you how it is set up; Set up opens it. If after an update one page matters more than any other — the cart, the members' area — put it in Page to check, and beside it the text that is always there (“Proceed to payment”). A broken page often still answers “all fine” but without its content: that text is the only way to notice from outside. If it fails, the update is rolled back.
7. 7Save. From then on the first check runs within a minute; Check now forces it immediately so you can see the outcome.

What it checks

• That the site answers, and how fast: an interval from 1 to 30 minutes, chosen per site. The minimum depends on your plan: five minutes on the free one, one minute on the paid ones.
• The confirmation threshold, that is how many consecutive failed checks are needed before declaring an outage. The usual value is three.
• The content of the page, not just the response code: it recognises the database connection error, the WordPress critical error, the blank page and an account suspended by the host. In all of those the server answers 200 OK and ordinary monitoring reports everything as fine.
• A keyword of your choice that must appear on the page (or must not). It covers the failures no list can predict: a vanished cart, a broken contact form, a replaced homepage.
• HTTPS certificate and domain expiry, with staged warnings at 30, 14, 7, 3 and 1 day — and two months ahead for the domain, because renewing one can involve steps that do not fit into an afternoon.
• From two places in the world, Amsterdam and Virginia. Each one checks the site on its own, with its own threshold, and an outage is declared only when both see it: a network problem between us and the site, or a host that filters the addresses of a whole continent, never becomes an alert. On the site’s page, Vantage points shows what each one sees and with what response times. If one of the two stops, the checks carry on from the other.

How to read the numbers

• Availability is measured over TIME, not over how many checks succeeded: under every percentage you get how much time we actually observed. “100% over 3 observed hours” and “100% over 30 days” are different things, and they should look different.
• Four windows: 24 hours, 7 days, 30 days and 12 months. The 12-month one is the number that ends up in contracts.
• Minimum, average and maximum response time over the last 24 hours, plus the chart: it is how you notice a site slowing down before it stops altogether. In the chart the “typical” line is the normal response and the light “peaks” band above it reaches up to the slowest response in each stretch; a triangle on the edge (“off the scale”) marks a peak beyond the scale, and the label at the top gives the highest one and when it happened.
• The outage list, with the cause in plain language (“the keyword disappeared from the page”) and the raw technical error underneath — the one to paste into a ticket for the host.
• Check now forces an immediate check without waiting for the next round: useful right after fixing something, to see whether it is back. It works up to three times a minute per site; beyond that, the button tells you how many seconds to wait.
• On the Monitoring page every site has its own card: in large type how it is right now (the response time, or how long it has not been responding), below it the thirty days as squares and three numbers — uptime, outages and certificate expiry. Above the cards, on one line, the numbers for the whole fleet and the filters. At the bottom, Latest outages gathers those of every site in the last 30 days, most recent first, with the cause written out: the site name opens its detail. The first five are shown; Show all opens the rest.

Performance, measured by Google

• The score is the PageSpeed Insights one, the same your client sees if they look it up themselves. We do not compute our own: a number of ours saying “good” where Google says 43 would be useless.
• It is measured once a week, on the mobile version — the one Google ranks on. More often would make no sense: the score moves when someone touches the theme, the plugins or the images, not from one day to the next.
• Next to the score is the change since the previous measurement: it is the line you use to show a client that the work paid off. It is missing on the first measurement, because there is nothing to compare yet.
• The three metrics below say WHERE the time goes: LCP is when the main content appears (usually an oversized image), CLS is how much the page jumps while loading, TBT is how long it ignores clicks because of scripts.
• The dot next to each metric uses Google’s thresholds: green, amber or red. The first measurement arrives within a few days of connecting the site, not immediately.
• Below the metrics there is What to do to go faster: the items come from Google with the estimated saving next to them — “compress the images · −2.4 s” — ordered by what pays off most. The score says there is a problem, this list says where to start.
• The AI copilot reads the same measurements and cross-checks them with the plugins you have installed, which Google’s report cannot do: “your LCP is 4.2 s and 60% of the weight is images — you have Elementor without an image optimisation plugin”. It does not cost an extra analysis: it travels inside the one you already ask for.

How to update in bulk

1. 1Open Updates: the list shows every available update with its site, the current version and the new one.
2. 2If a version is unfamiliar, open the changelog from its row: you read it there, without hunting for it on wordpress.org.
3. 3Tick the rows you want to update. You can select the same plugin across several sites in one go.
4. 4Check that Safe Update is on: it is the switch in the bar below the list, and it takes a database backup before anything is touched.
5. 5Press Update selected, in the same bar below the list, and let it work. On a long list the bar stays at the bottom of the screen, so you don’t have to scroll back up. When it finishes each row carries its outcome, and the activity log keeps the record.

What happens if something breaks

• Before updating, with Safe Update on, a copy of the site's database is saved.
• After the update Tendfolio calls the site back to verify that it still responds and is not showing a critical error. It checks the homepage and, if you named one in Page to verify, that one too: that is where the failures a homepage hides show up.
• If the site no longer answers, plugins and themes are rolled back to the previous version automatically, without waiting for you to notice.
• Either way you get an alert with what was updated, what failed and what was rolled back.
• How each plugin updates is chosen from the site’s Plugins tab: automatic updates (WordPress does them as soon as a version is out), manual updates (you do them from Tendfolio, with a backup first) or locked. Automatic is handy for security plugins, best avoided for anything that touches the layout.
• From a site’s page, Safe update first shows what will be updated and what will happen. Then a card at the top follows the steps — backup, updating one component at a time, site check — and at the end says in one sentence how it went: all good, something failed, or back to the previous version. You can keep working while it runs.

Updates made outside Tendfolio

• The Update button in wp-admin is one click away, and WordPress auto-updates ask nobody's permission. Tendfolio sees them anyway: the connector reports the moment it happens, not at the next scan.
• In the log you find what changed, from which version to which, and from where: the WordPress panel, an automatic update, or the command line. If it was a site user, who it was as well.
• Right afterwards Tendfolio checks that the site still responds, using the same pages as a safe update. If it broke you get a high-severity alert naming the component that was touched.
• Tendfolio never rolls anything back on its own. An update you did not ask for may have been wanted by somebody else — the client, a colleague — and undoing it behind their back would be worse than the fault.
• For 48 hours the site page shows a banner with Roll back: you press it, after reading what would revert and to which version.
• It rolls back the code, not the data: if a plugin changed the database while updating, those changes stay. To roll back the data too you restore a backup.
• If a plugin kills WordPress outright — fatal error, blank page — the site can no longer speak, but a small watchman installed alongside the connector can: it survives the failure and tells you which file caused it. It only reports; it never deactivates anything by itself.

Choosing what to update from the Overview

1. 1In To do, press View on the “N plugin and theme updates” row: the row opens and lists the plugins one by one, with versions and which sites.
2. 2Untick the ones you don’t want to update now. New major versions (for example from 3.x to 4.x) start unticked: read what’s new first.
3. 3Press Update N of M: only the ticked ones run, with Safe Update if your plan includes it.

How to lock a plugin

1. 1Press Lock next to the plugin, from the open row on the Overview or from the row’s padlock on the Updates page; on the site’s Plugins tab choose Updates locked in the row’s menu.
2. 2Choose where it applies: on all sites, including those that install it later, or on one site only.
3. 3Write why, if it helps the team: “4.4.12 breaks the client’s theme” shows next to the lock.
4. 4Keep Also stop WordPress automatic updates ticked if they are on for the site, then press Lock.

What a lock does

• The plugin stays at its current version: it no longer shows among things to do, it doesn’t count as an update and bulk updates skip it.
• It applies everywhere: the Overview, the Updates page, the API, Tendfolio AI and the Fix button on security alerts.
• With connector 2.37 or newer the site also stops WordPress automatic updates for that plugin. With an older connector the lock only applies to Tendfolio.
• The Update button in wp-admin stays: whoever works on the site can still update it by hand, and Tendfolio records it as an update made outside.
• Locks are at the bottom of the Updates page, with what they hold back, why and who set them; Unlock puts the plugin back among things to do.

How to look at the visual comparison

1. 1When an update changes how a page looks by a lot, you find it in To do and at the top of the site’s Overview (“An update changed how the site looks”), and you get an alert.
2. 2Press See before and after: on the left the pages checked with how much is different, on the right the two screenshots side by side with the changed areas outlined in red. Zoom in shows them at full size and scrolls them together; a click on an outline takes you straight there. Slider overlays them and you compare by dragging; Differences only shows the after screenshot with the areas filled in. Hold Ctrl (⌘ on a Mac) and use the wheel to zoom in and out where your mouse points.
3. 3If the change is intended — a plugin that redesigned its look, a new banner — press Looks fine: the alert goes away and the update stays.
4. 4If something broke, press Roll back: the plugins and themes of that run go back to their starting version. The database stays as it is, so changes made in the meantime are not lost.

What to know about the visual comparison

• It is part of the safe update, from Pro up: before updating Tendfolio takes a screenshot of the homepage and of the check page you chose, and takes them again afterwards.
• It alerts you when at least 5% of a page is different. It counts areas, not single pixels, and the part you see on opening weighs on its own: a broken hero doesn’t get lost in a long page.
• It doesn’t roll back on its own: automatic rollback stays for real failures, when the site doesn’t respond or shows an error. A change in look is your call.
• Areas that change on every visit — cookie banners, chats, videos, embedded content, carousels — are left out and shown striped. To recognise carousels and dates the page is captured twice before the update.
• Screenshots go up to 3000 pixels tall and are kept for 30 days. A page behind a password is captured as a visitor sees it: the comparison covers the public part.

How to install across several sites

1. 1Open Install plugins — from the menu on the left, or from a site’s Plugins tab, which opens it with that site already ticked — and search by name or by what it does, or use the shortcuts under the search (SEO, Security, Cache…). The search queries wordpress.org and works better in English: “contact form” finds more than its translation.
2. 2Open the details if you want to check rating, active installations and the date of the last update — a plugin untouched for two years is a risk, not a saving. The tabs hold the full description, the latest reviews, what’s new in recent versions and the FAQ; Add to install sits at the top, next to the icon.
3. 3Press Add: the plugin goes into the To install panel on the right (on a phone, at the top of the page). You can add more: each one has its own sites to tick and its own Activate switch, because the right site for one plugin is not necessarily right for another. Press Chosen again to remove it.
4. 4Once every plugin has at least one site, press Install: Tendfolio installs each one on its own sites and shows the outcome plugin by plugin, row by row. Sites that already have a plugin are marked “Already installed” and cannot be ticked.

Worth knowing

• Most used in your fleet shows what you already have elsewhere: it is how you avoid ending up with two plugins doing the same job on different sites.
• A paid plugin is uploaded as a .zip and installed where needed, exactly like the ones from the catalogue.
• The Activate after install switch starts on: turn it off if you only want to upload the plugin and activate it later from the site card.
• Activation, deactivation and deletion happen on the individual site’s Plugins tab. Only an inactive plugin can be deleted, and the dashboard asks for confirmation on the row first.

How to close an alert

1. 1Open Security: alerts are sorted by severity and each row says which sites are affected. Vulnerabilities of the same plugin share a single row (“Contact Form 7 · 5 known vulnerabilities”): one update usually closes them all, and opening the row shows them one by one.
2. 2Click the alert: its card opens on the side, with the list still in view. At the top, the kind of flaw in plain words and, below, What’s at risk: who can exploit it and what they get, in one sentence.
3. 3How to fix it has a single button: it updates the component on every affected site — with Safe Update, if your plan includes it, a backup first and automatic rollback if the site stops responding. Only here, next to a site, updates that one alone. It only starts when you press it, never on its own. After the click the card follows the work site by site — backup, update, check — and, once the security check Tendfolio re-runs by itself is done, says whether the vulnerability is closed, still open, or whether Safe Update had to put the site back as it was.
4. 4If the alert does not apply to you (it happens: a generic check against a site with particular needs), press Ignore. The rule sticks and the alert does not return at the next scan.
5. 5Run the scan again to verify: the score updates and the alert leaves the list.

What you see

• A score from 0 to 100 for every site and a fleet average: it is there to tell you where to start, not to boast about.
• Known vulnerabilities with their CVE code, severity and the version that fixes them — which almost always means: update that plugin.
• Configuration checks: the file editor in the dashboard, a user called admin, exposed XML-RPC, missing HTTP security headers, WordPress and PHP versions visible from outside.
• The site's WordPress users: who they are, their role, when they last signed in. From here you block the ones no longer needed.
• A scan can be launched by hand on one site or on the whole fleet, and runs by itself at regular intervals anyway.
• On a site’s page, opening an alert shows, in this order: which component it concerns and what kind of attack it is, the facts that identify it (installed version, publication date, weakness type), what to do — with the version that fixes it and the button to update safely, or the explanation when no fix exists — and then the original advisory text, with its sources.
• The card also says how many other vulnerabilities the same update closes: for WordPress core or an outdated plugin it is often dozens of alerts at once, and the best reason to do it now. Next to each site you see whether it has a backup. Affected versions, flaw class, the feed’s original text and sources sit under Technical details, closed until you need them.
• At the top of the page, the fleet verdict: “At risk” has a pulsing red beacon, the other states a steady light. In every row, “2 of 2” and the small bar say how many of your sites that alert affects: red when it affects all of them.

How to read it and fix it

1. 1The check starts off on every site: open the site, go to the Links tab and turn on the Check enabled switch. The first pass starts straight away.
2. 2Each box is one address that no longer responds: at the top you get the reason — “the domain no longer responds”, “the page no longer exists” — and the address itself, clickable, so you can see for yourself.
3. 3Below are the pages where that address is written, with the clickable text in quotes: that is how you find it inside the article.
4. 4Edit in WordPress opens that page ready to edit, with no password. Fix the address or remove the link, and save.
5. 5At the next check the entry disappears on its own. If you are in a hurry, Check now runs the pass immediately.
6. 6If you no longer need it, turn the same switch off: from then on Tendfolio sends no requests to those addresses.

What the system decides

• The pass runs daily and looks only at published content, up to 400 links per site.
• Entries are grouped by address, not by page: the same dead address written in four places is one problem with four fixes, not four problems.
• A 404 is reported straight away, because the server itself says the page is gone. A network error or a 500 must repeat for three passes before it shows up: servers hiccup, and a list that cries wolf stops being read.
• A 401, a 403 or a 429 is not a broken link: the page exists and is turning robots away. We don't report those.
• Links that failed once or twice are counted at the bottom as “under watch”: we are keeping an eye on them, but we don't call them broken yet.
• Stop reporting it applies to the whole address and deletes nothing: it stays in the counts, it leaves the list of open problems.
• When there are broken links the site overview says so with a notice, and the number of addresses appears on the Links tab: you don't have to open it to find out.
• The check is switched on per site, not per organisation: you can keep it on for three sites and off for the rest, and sites that are off are not queried at all.

How to restore a backup

1. 1Open the site card and go to Backups: the copies are listed by date, with type, size and expiry day.
2. 2Pick the copy to put back. When in doubt take the last one before the problem, not the most recent one.
3. 3Press Restore and confirm. The restore happens in chunks, so even an archive of hundreds of megabytes does not time out halfway.
4. 4Wait for the operation to finish before taking the site out of maintenance: at the end Tendfolio checks that the site answers again.

How backups work

• Database only is a compressed dump: light, fast, and it holds content and settings. Database + files adds a zip of wp-content, so themes, plugins and media.
• Scheduled backups are set per site: how many hours apart, at what time and how many days to keep them. The starting period is your plan’s; for a site you can only shorten it, and the new period also applies to backups already taken, counted from each one’s date.
• Before every bulk update a safety copy is taken, if Safe Update is on: that is what makes the automatic rollback possible.
• Downloads go through an expiring link: you can send it to an outside developer without giving them panel access.
• In the Backup tab, above the copies, three cards tell you where things stand. Automatic backups says whether they are on or off; the switch turns them on and off right away, and Change time and contents picks when and what to save. Retention says how many days copies are kept, compared with your plan’s maximum, and that is where you shorten it. Storage shows how much of your plan’s storage is used, shared across all your sites; the ⓘ shows how much this site uses and how much the others do. When it is running out, a notice above the copies says how many more full backups of the site fit.
• A manual backup starts from two places: Back up now in the site header, from any tab, and Create backup, the header’s filled button when you are in the Backup tab. Both ask what to save: the database only, or database and files.
• Database size isn’t an obstacle: the dump is written and read back in chunks, on the site and here, and from connector 2.41 restores import it in slices too. So even shops with years of orders are backed up and restored like any other site. With an older connector, a restore imports the database in a single request, which on a very large database can take longer than the hosting lets a request run.
• The file archive also contains the site's wp-config.php, with the database credentials but without the session keys and salts: those can forge an administrator sign-in, so they never leave the site. You need it the day you rebuild everything elsewhere: new ones are generated there and whoever was signed in signs in again. A normal restore never touches it, because overwriting a live site's configuration with a three-week-old one would take it down.
• Every night Tendfolio re-reads each site's copies and checks that they are intact: the database dump line by line, the file archive from its internal index, and — for copies that build on a previous one — that every link in the chain still exists. A file that arrived half-written is found now, not on the day you need it. If a copy does not hold up, you get an alert.
• Site size no longer blocks a backup: the connector works in short slices and resumes where it left off, so no single request lasts long enough for the host to cut it off. On very large sites the archive is built in several parts, applied one after another on restore.
• Not every file copy weighs the same, and that is deliberate: when the site has changed little, Tendfolio saves only the difference from the previous copy instead of rebuilding the whole package. In the list that copy looks tiny, but it restores like any other — Tendfolio puts the pieces back together at restore time. Every so often it starts again from a whole copy, so the chains stay short.
• If not a single file changed on a given day, no new copy appears for that day: the site diary shows a “No files changed” entry and the previous copy stays valid. It is not a missed backup, and that is why no alert reaches you.
• A Database + files restore puts the site back as it was even for what appeared after the backup: plugins, themes and mu-plugins added later are removed, and so are code files that showed up among the media or in the wp-content folder — that is usually where whatever an attack leaves behind hides. Photos and documents uploaded later stay: they are the client’s work. The Tendfolio connector is never touched. It needs connector 2.36 or later: with an older one, files created after the backup stay where they are.
• From connector version 3.3 every site signs its backups as they are made, with a key that stays on the site only: the list shows “Signed by the site”. From 3.4, in a restore, the site checks every file and every piece of the database before writing anything, and an altered backup is refused without touching anything: not even someone who took control of Tendfolio could put invented files or data back on it. The first file backup after the update is always complete: it is where the signatures start.
• Backups without the site's signature — made before 3.3, or by another installation of the same site — go through only if whoever runs the site allows it in WordPress, Settings → Tendfolio, Allow for 24 hours. Tendfolio asks every site with connector 3.4 for this at its first check. The window closes by itself after 24 hours or at the first completed restore.

How to clone a site

1. 1Open the site to copy and, at the top, press ⋯ next to Open WP-Admin: choose Clone onto another site.
2. 2Under Onto, pick the site that will become the copy. Sites that can’t be chosen stay in the list, each with its reason.
3. 3Under Backup, the latest full backup is already chosen. You can pick an older one, or Make a full backup now if you want a copy of the site as it is right now.
4. 4Read the two columns — what gets replaced and what stays — and the preliminary check, then type the destination site’s name and press Clone onto….
5. 5The panel takes you to the destination’s page and shows where it’s at: backup of how it was, files, database, addresses. The outcome also stays in both sites’ activity log.

Filling a site you’ve just connected

1. 1Connect the new site from Add site, even if it’s a fresh WordPress install.
2. 2As soon as it’s connected, Tendfolio asks “How do you want to start?”: choose Copy another site, then the site to copy, and press Continue.
3. 3In the window that opens, pick the backup — the latest full one or one made now — type the new site’s name and confirm.
4. 4If you skipped the question, the Overview of the still-empty site shows Fill from another site: it leads to the same window.

What to know before cloning

• Everything in the database and in wp-content is replaced on the destination: posts, pages, media, users with their passwords, plugins, themes and settings.
• The destination keeps its address and its connection to Tendfolio, with alerts, scheduled backups and monitoring as you had set them.
• The source site’s addresses inside the content become the destination’s: including data WordPress stores in serialized form and page-builder JSON like Elementor’s, with and without https.
• The two sites can have different table prefixes (wp_, wpx_…): Tendfolio detects it and adapts everything, user permissions included. Tables of other installs living in the same database aren’t copied.
• Before touching the destination, Tendfolio takes a full backup of it. If that fails, the clone doesn’t start; if something breaks halfway, the site goes back to how it was on its own. That backup stays in the list: if you change your mind, restore it whenever you like.
• To receive a clone, the site needs connector 2.40 or later. The source site works with any version, because the clone starts from its backup.
• Multisite installs can’t be cloned, neither as source nor as destination.
• You need permission to restore backups and access to both sites. It takes a few minutes, longer for a large site; you can close the page, the work carries on.
• Before starting, Tendfolio always runs a preliminary check: free disk on the destination, PHP extensions, backups or imports in progress, size of the database and of the backup, backup space. If something would stop the copy it says so up front, with the reason, and the button stays off; the check runs again when you start.
• From connector 2.41 the database is imported in slices, the same way it’s backed up: no request lasts more than about fifteen seconds, so its size is no longer a limit — what counts is time and the destination’s disk, which for a moment also holds the uncompressed dump. Files travel in parts, and an incremental backup is applied layer by layer: even a site of many gigabytes is copied. With an older connector the database is imported in a single request, and above roughly 10 MB compressed the clone doesn’t start.
• You also reach the same window from the ⋯ of a copy in the Backup tab, with that copy already chosen: use it to clone the site as it was on a given day.
• From connector version 3.4 the destination accepts only backups it signed itself, and a clone brings another site's: before cloning, whoever runs the destination opens WordPress, Settings → Tendfolio, Allow for 24 hours. The pre-check says so before starting, and the window closes by itself once the clone is done.

How to generate an article

1. 1Open Content. The generator has four numbered steps: in step 1 “Which site” tap the card of the site to publish on. With more than six sites, only the chosen one’s card stays: Change site opens the list with search, by name or address, and the recently used sites at the top. From a site’s page, the Content tab → Write with AI has the site already chosen.
2. 2In step 2 “What it is about” write the topic, or leave the field empty: in that case the AI looks at the site's categories and its published articles, and picks a new one that is not a duplicate.
3. 3In step 3 “What it looks like” adjust if needed: length with the buttons from Flash to Guide, images and number of articles with − and +, tone, language and category from the three menus below. The starting values are right almost every time.
4. 4In step 4 choose where it ends up: Draft (you review it), Publish now or Schedule. With Schedule the month calendar appears: tap the days the articles should go out, one per article, and pick the time. A step’s number turns into a tick once it has what it needs; on the right the summary shows site, topic, articles, destination and when each one goes out, with the credit cost and how many you have left — if they are not enough, the button is off and the summary says how many are missing, with Buy credits leading to the packs in Plan & credits (for whoever manages the subscription; everyone else is told whom to ask).
5. 5Press Generate. The article appears in the list below and moves along by itself: writing, images, publishing. At the end you get the link to open it in WordPress.

What the AI decides, and what you decide

• You decide: site, topic (if you want one) and destination. The rest — length, images, how many articles, tone, language, category — starts preset and changes with one click.
• The AI decides: title, excerpt, slug, categories, tags and the image prompts.
• The starting language is the site’s, not the panel’s: an English site gets an English article even if you use Tendfolio in Italian. If you need a piece in another language, pick it from the language menu.
• Images are uploaded to the site's media library like any other image, cover included: they stay yours even if you stop using Tendfolio tomorrow.
• If something fails halfway, the credits come back. If the article was published but an image was not, the article stays and the missing image is flagged.
• The editorial plan generates N articles every X days with the parameters you chose, and stops by itself when it reaches the monthly spending cap you gave it.
• When you schedule several articles, each one gets its own day: the calendar suggests one a day starting tomorrow, and you change them by tapping (one tap removes, another adds). They are numbered in release order. The time applies to all; for a different time on one day, change it in the list next to the calendar. Until the chosen days match the number of articles, or while a time today has already passed, the button stays off. The AI picks the articles while generating: to put a specific article on a specific day, afterwards press Change date next to it in the list.

How to send a report to a client

1. 1Open the site card and go to Client report.
2. 2Choose the period — 30, 60 or 90 days — and press Generate report.
3. 3Read the AI summary: it is in plain language, written for someone who does not know what a CVE is, and built on the real numbers of that period.
4. 4Copy the public link and send it to the client, or open the report and print it to PDF if they prefer an attachment.
5. 5If you want it repeated, switch on the automatic report: it is generated and sent every month without you remembering.

What it contains

• Availability for the period, with minutes of downtime and how many episodes there were.
• The updates applied, split between core, plugins and themes.
• Security alerts closed and still open, with their severity.
• The backups taken during the period and when the last one was.
• A written summary that ties the numbers together, so the client understands what was done without having to interpret them.

How to set it up

1. 1Open Settings → Brand. If your plan does not include it you still see the screen, switched off, with what it would change.
2. 2Type the display name: it is what the client reads at the top of the report. Leave it empty and we use your organisation's name.
3. 3Upload the logo — PNG, JPEG or WebP up to 512 KB. Which version you need, the light or the dark one, the screen tells you itself based on the background you picked; the preview next to it shows how it really looks.
4. 4Pick the header background: it is the band at the top of the report and the email. Leave it empty and it stays the usual black, which is made to be printed and filed. We do not ask you for the text colour — we work it out from the background, so on a light background the writing turns dark instead of vanishing.
5. 5Pick the accent colour: it tints the rule above the header, your name and the button in emails. If it does not stand out against the background you picked we tell you, and use the text colour instead: an invisible accent is worse than none.
6. 6Write the closing line — for instance “Looked after by Studio Rossi · studiorossi.it” — and save. It applies from the next report.

Where it shows, and where it does not

• It shows: header and footer of the client report, both on the public page and in the printed PDF.
• It shows: the automatic report email that reaches the client, with logo, colour and closing line.
• It does not show: the panel, the alerts that reach you and your team, Telegram notifications.
• The brand is frozen into the report when it is generated: if you change logo in November, June's report stays as it was when you sent it.
• If you drop to a plan without branding, documents go back to your organisation's name — the settings stay written and come back if you move up again.

How to invite someone

1. 1Open Team and press Invite user.
2. 2Type the email address and choose the role: Owner, Administrator, Member, Client or Read-only.
3. 3Adjust the permissions if you need to: roles are starting points, not cages.
4. 4Choose which sites they get access to — all of them, or only the ones you assign. Client and Read-only start from assigned sites: tick the ones they should see.
5. 5Press Create invite: Tendfolio gives you a link that expires, which you copy and send to the person yourself — no email goes out. With that link they set their own password: you never see it and never have to invent one for them.

How the roles work

• Owner — can do everything, including plan, billing and removing other members. Usually there is only one.
• Administrator — manages sites, updates, security and the team, but does not touch billing.
• Member — works on the sites assigned to them: updates, backups, wp-admin access, resolving alerts, asking Tendfolio AI. This is the role for whoever is in production.
• Client — read-only on their assigned sites: state, security, reports, backups to download and the activity log of their sites, plus the AI suggestions. Of the alerts they get monitoring and security; update and backup alerts go to the people who work on the sites. They don’t ask Tendfolio AI questions and don’t generate or send reports: those use credits and write to third parties. Read-only is the same, without backup downloads.
• If the five roles are not enough, there are twenty-five granular permissions to combine as you like.
• The site limit applies everywhere, not just on the pages: in alerts, in the live updates the panel shows, in tags and in update locks. A client who sees only their own site does not even get the names of the others.
• If the plan no longer holds someone — it happens after a cancellation, when the organization goes back to Free — that person stays on the team with “Suspended” next to their role and can’t sign in. The owner stays in, and, up to the team limit, whoever joined first. No data is lost: moving to a plan that includes them lets them back in by themselves.

How to connect Telegram

1. 1Open Settings → Notifications and turn on the Telegram switch. Telegram is included from Pro; on Free, alerts arrive by email and in the dashboard.
2. 2Follow the link that opens the conversation with the Tendfolio bot and press Start.
3. 3Back in the panel the state becomes “connected and active”. From there you choose which categories go to Telegram and which go by email.

What you can receive

• Monitoring — site unreachable and back online. These are the urgent ones, the ones worth sending to Telegram.
• Updates — new plugin and theme updates available. Fine by email, once a day.
• Security — known vulnerabilities found by the scans.
• Backups, content and billing — outcomes of scheduled backups, generated articles, plan renewals.
• An outage sends one alert, not one a minute, and a second one when the site comes back: if the phone rings twice, the story is over.
• For a single site you can decide differently: in its monitoring settings, Who to alert and how chooses who gets that site’s alerts and on which channel, and adds addresses outside the team. Where nothing is chosen these preferences apply; the master switches for email and Telegram stay yours.
• Alerts follow the team’s limits: an alert about a site reaches — in the bell, by email and on Telegram — only the people who can see that site; security flaws only those allowed to see security; failed backups and backup storage running out only those who make backups. The owner receives them all.

How to create a key

1. 1Open Settings → API and press New key.
2. 2Give it a name that says what it is for: in six months “test 1” will mean nothing.
3. 3Choose the scopes one by one. Give only what is actually needed: a key that reads state does not need to be able to delete backups.
4. 4Copy the key and store it straight away: it is shown in full exactly once and cannot be recovered afterwards.
5. 5Use it in the Authorization header of your requests. Next to the key the panel tells you when it was last used.

Worth knowing

• Every key carries only the scopes you gave it, and you can review them at any time.
• There is a rate limit per key: it stops a misbehaving integration from hammering your clients' sites.
• A key can be revoked whenever you like, and stops working instantly from that moment.
• The full endpoint reference, with curl examples and responses, is in the API documentation.

How to change your photo and name

1. 1Open Settings → Profile & sign-in.
2. 2For the photo press Change photo: pick one of Nova’s sixteen expressions, or switch to Your photo, drop a file (JPG, PNG or WebP up to 10 MB) and crop it inside the circle with the zoom. Press Use this one or Save photo: it changes right away, in the menu and in the team list.
3. 3For the name press Edit next to it, type the new name and press Save.
4. 4We send a 6-digit code to your account email: type it in the boxes that appear under the field. It lasts 10 minutes; if it doesn’t arrive, Resend it.
5. 5With the right code the name changes. The email can’t be changed from here, because it’s the address you sign in with: to change it, write to support.

How to download an invoice

1. 1Open Settings → Invoices.
2. 2You’ll find your organisation’s invoices and credit notes, newest first, with number, date, amount and status (paid, fully or partly refunded).
3. 3Press Download on the row you need: the PDF is saved to your computer, with the document number in the file name.
4. 4To change your card or billing details, or cancel your subscription, press Manage card and subscription at the bottom of the page: it appears when you have an active subscription or a storage pack.

If you forgot your password

1. 1On the sign-in page, press Forgot password?.
2. 2Type the address you registered with: you get an email with a link, valid for one hour. Only the most recent link works.
3. 3Open the link and choose a new password, meeting the requirements shown under the field.
4. 4Sign in again with the new password. Sessions open on other devices are closed, and you get an email telling you about the change.

How to delete your account

1. 1Open Settings → Profile & sign-in and scroll down to Delete account.
2. 2Press Delete my account… and read the list: which organizations will be deleted and which you will only leave.
3. 3Confirm by typing your password — or your email address, if you only sign in with Google.
4. 4Press Delete permanently. You are signed out and receive a confirmation email.

How to open a request

1. 1Open Support from the side menu, at the bottom. At the top, in How can we help?, describe the problem in a few words: we suggest the passages of the guide that cover it, and you can pass the same question to Tendfolio AI. If that isn’t enough, press Write to our team or New request in the Write to us box: the form opens in a panel on the right, with the subject already filled in. Next to your requests you see whether a Tendfolio service has problems right now.
2. 2Write a subject that states the problem in one line and pick the topic: technical issue, billing and plans, account and sign-in, other.
3. 3If the problem concerns a site, pick it: whoever replies can open it without having to ask you which one.
4. 4Describe what you were doing, what you expected and what happened. Attach up to four screenshots (PNG, JPEG or WebP, 5 MB each).
5. 5Press Send request. When we reply you get an email; the conversation continues on the request’s page.

What to know

• Priority is set by the plan, not by who writes: on paid plans requests have priority and move ahead of free-plan requests in the queue. Support can raise the priority of a serious case by hand, and the request then says so.
• If you move to a paid plan while a request is open, it becomes priority with your next message. Priority never goes down on its own.
• Requests belong to the organization: every member can see them, and anyone can add details. They stay even if whoever opened them leaves the team.
• The status tells you whose turn it is: “In progress” means it’s on us, “We replied” means it’s on you.
• Once the problem is solved, Mark as resolved closes the request. If you write again on a resolved request, it reopens by itself.
• Reply emails are a notice, not a channel: if you reply to the email, the message doesn’t reach the request. Reply from the dashboard.