One password for your whole site, checked where nobody can read it

Some sites are not meant for everyone. A family album, a client preview, a wedding page, notes for a small team. You do not want accounts for all of them. You want one password you can share in a message.

Kreova can now do exactly that, and do it properly.

The problem with a password in the page

A password screen looks secure. But if the check is written into the page's own script, the password travels to every visitor's browser, where anyone can read it. And the data behind that screen has to be public for the page to load it, so it can be fetched without typing anything at all.

Until now, that was the easy thing for a builder to write when someone asked for an entry password. It looked right and it did not protect much. So we closed that gap in the platform.

What happens now

Ask for it in a sentence:

Everyone has to enter a password to see this site.

Kreova asks what the password should be if you have not said, and never makes one up. Then the server guards the whole site:

• Nothing loads without it. Every page, row of data and file answers "not allowed" until the right password is entered. A page you add next month is covered too, with nothing to remember.
• Search engines stay out. They are told not to read the site, and they cannot get past the password anyway.
• Visitors only enter it once. A browser that gets it right stays let in for 30 days.
• Guessing is limited. Each visitor gets 10 tries an hour.
• The password page matches your site. The builder can style it in your site's look, with no private words on it, because it is the one page a stranger can see.

Your preview in the builder does not ask for it, so you can keep working as normal.

Your password stays yours

Kreova keeps only a scrambled copy, so it cannot be shown again, by us or by anyone. If you type the password in the chat, the moment it is set your message shows dots instead, and the builder says "the password you chose" rather than repeating it. Keep your own copy somewhere safe.

You can change it or turn it off any time under Services, Site services. Changing it signs everyone out, so they all need the new one.

When to use accounts instead

It is one password shared by everyone, so it cannot tell people apart. If different people should see different things, like customers seeing only their own orders, ask for accounts and access rules instead. Kreova has those too.

Already have a password screen?

If your site has a password screen that was written into its pages, tell the builder:

Replace my password screen with the site password. The password is the one I will set under Services, Site services.

Then set it there. If you want a private site, this is the version that keeps it private.