The Publish button in Studio's toolbar stays visible in a narrower window. When space runs out, secondary buttons show only their icon, and their name appears on hover.
Pressing Publish again on a version that is already published no longer ends in an error.
When a domain's DNS records are changed to point at the site, its status no longer keeps showing the old records for about an hour. Check status also sees the change right away. Read more: Connecting to a site
You can connect your own AI app without an existing account: choose Create account on the sign-in page and give your team a name. Read more: Connecting an app
An app connected to the whole team at the edit level can create a new trial site and build its content itself. Read more: Creating a new site
An app can draft an order for a site's plan and domain, which you confirm and pay yourself, and link a team domain to a published site. Read more: Ordering a plan and a domain
If a site's build fails after a publish, the site's people get a notification. It can be muted like other notifications.
Publishes from Studio and from apps show in the team's activity and the site's deployment history.
An AI app connected to a whole team can be given extra permissions: reading contact requests, reading invoices and billing details, and starting a domain purchase. The app pays nothing: it makes a draft order that you confirm and pay yourself. Read more: Your own AI app (MCP)
Under Connected apps in your profile, each app's recent actions are listed, and a site's History page shows the changes apps have made. Besides changes, reading contact requests, invoices and document contents is recorded.
You can connect your own AI app to a whole team: it then reaches all the team's sites, including ones added later, and its documents. Alternatively you can grant access to chosen sites only. Read more: Your own AI app (MCP)
The app can set a password on a document's public link when publishing, or remove it.
The connection page is reworked. You choose one permission level (read, edit, or edit and publish), and above the buttons it shows what you are about to grant.
Your own AI app can also create and edit your team's documents, for example write a new contract or offer. At login you choose the teams and permissions for documents separately. Read more: Documents with your own app
Your own AI app (MCP) has its own section in the guide, with instructions for connecting Claude, ChatGPT and Claude Code.
You can edit your site with your own AI app, for example Claude or ChatGPT. The app connects to mcp.kotisivukamu.fi, and at login you choose whether it may read, edit or also publish. This also suits a marketing agency you have invited to the site. Read more: Your own AI app (MCP)
In WhatsApp your message is marked as read and you see the typing indicator as soon as Kamu starts working on it.
The editor on the Posts page shows the cover image under the image field.
If the site's file has changed since you started editing a post, the editor says so above the text. You can view the differences and choose whether to use the site's version or keep your own draft.
Several messages sent in a row are handled in the order they were sent, both in WhatsApp and in the dashboard chats.
A blog post can be written and updated in WhatsApp. Kamu saves the text as a draft, and it is published with the Julkaise button in the message. Read more: WhatsApp
Kamu can read a web page whose link you send in the conversation and use it, for example, as a source for a blog post.
A site draft can be discarded and started over from the published version. The discarded draft is kept and can be restored. Read more: Discarding a draft
Versions are named automatically from the first request, and the name can be changed from the version menu.
The status of signature requests is available at any time from the editor's Signatures button. There you can send a link again, cancel a request, add a signer in place of a cancelled one and download the signed PDF. Read more: Signature requests
Studio has been redesigned. You edit the site by chatting with Kamu, and the preview updates as changes are made. Text can be edited directly in the preview, and the Pick what to edit tool lets you point at the part you want changed. Save stores your changes in a draft, and Publish puts them on the site.
If the previous editor had unpublished changes, they appear in the new Studio as an unpublished draft.
On the Documents page you can create documents, presentations and pages with Kamu, organise them into folders and choose whether the whole team can see them. Read more: Documents
A brand book can be created from an existing website: the logo, colours and fonts are taken from the site.
A document can be sent for signature. The signer gets a link, sees the document as a PDF and confirms the signature with a code sent by email. The finished PDF with its certificate is sent to every party.
Contact form submissions are checked for spam. Suspicious messages go to the Spam section of the Contacts page, from where a genuine message can be delivered. Read more: Notifications
The shop notifies you by email and in the notification bell when Stripe starts accepting card payments for the shop. The notification can be switched off in the shop's notification settings.
Shop shipping methods can have weight tiers, so the shipping fee follows the order's weight, and a delivery time shown to the customer at checkout. See Verkkokauppa.
Your Shipit account's prices show in the method editor, and Käytä Shipit-hintoja copies them in as the price and tiers. Methods fetched from Shipit arrive priced.
The shop's fetch-from-Shipit dialog shows the common parcel and pickup-point services first, preselected. The account's other services open from a separate link. See Verkkokauppa.
Web shop (beta): a site can carry a web shop where you manage products, orders, discount codes, shipping methods and invoicing details, and see sales statistics. The shop is enabled for a team on request. The assistant can list products and orders and propose product changes, which you confirm yourself.
In visitor statistics, Google Display ad clicks are gathered into one source and classified under the Display channel. Search ad clicks are now separated from organic search into a Paid Search channel.
The Domains page has a search for finding a domain by name.
On the site's front page, a Domain settings button sits next to the public address. If the domain is registered with Kotisivukamu, it opens its settings. Otherwise you see the domain's current nameservers, the likely DNS service and the registrar, and a button to start a transfer.
Domain changes, such as DNS records, nameservers, redirects and email settings, are recorded in the team's activity log. Failed changes show up there too.
The domain page shows when the domain was last changed and when its details were last updated.
An unpaid domain order can be paid directly from the domain page.
The WhatsApp assistant now replies when a voice message is too long or can't be processed, and asks you to send the changes as shorter messages. Previously there was no reply at all.
When the status of your support request changes, you may get an email about it. You can reply to it directly, and your reply is added to the same support request.
The English and Swedish versions of the dashboard are fully translated. Texts for domains, DNS settings, service keys and email setup were partly shown in Finnish before.
Studio's help text now says Pysäytä (Stop), matching the button.
The Search engines page has a Korjaa (Fix) button on the structured data check. It starts a site update, and the site is checked again after the update.
A domain transfer requires a transfer key, and registering or transferring a .fi domain requires a business ID or personal identity code. Required fields are marked on the form. See Domain transfer.
When creating a new site you can choose Ei logoa, käytä pelkkää tekstiä (no logo, text only). The site header then shows the business name. See Your first site.
WhatsApp works like the dashboard assistant: you don't pick a site, Kamu works it out from the request. After a pause of more than two hours, a new topic starts a new conversation. See WhatsApp.
The help button opens Kamu, the dashboard assistant. It answers questions about anything you can see in the dashboard, links to the right page, and files a support request when needed. See AI assistant.
Kamu can make changes after you confirm them: DNS records, publishing a site on a domain, new sites, deleting drafts, site settings, texts and blog post drafts.
When a domain is connected to a site, the www address points to the site too. Email records and other subdomains are left untouched. See Connecting a domain.
Files can be attached to the contact form. Attachments can be downloaded from the contact requests and are deleted automatically after the retention period. See Site structure.
A domain can be moved to another team from the dashboard. This requires admin rights in both teams, and future renewal invoices go to the new team. See Your own domain.
Studio tells you when unpublished changes are being fitted onto a published site that changed in the meantime. In a conflict you can ask support for help directly.
A purchased domain is no longer connected to the site automatically. Overview lists the team's unconnected domains, and a ready domain can be connected with Liitä sivustoon (Connect to site).
Studio shows your name or email address instead of an ID.
Images and PDFs attached in Studio are saved, but Kamu reads them only if you switch on the eye toggle. This keeps the conversation cheaper. See Studio.