It’s easy to share your static site with anyone, and allow anyone to edit it, without new users having to create a CloudCannon account. Allow me to (re)introduce a feature we call Client Sharing, available for users on any paid plan.
Client Sharing lets Organization Owners and Developers set a password to grant access to any user, allowing them to edit any site’s content. (Without access to complicated developer features.)
Even better, it works exactly the same no matter which static site generator you’re using on CloudCannon — meaning that sites built with Astro, Eleventy, Hugo, Jekyll, SvelteKit, Next.js, MkDocs, Gatsby, or Nuxt.js can all be edited by anyone: clients, external collaborators, content reviewers, subject-matter experts, legal teams, or anybody else involved.
Your site security is important, so the Client Sharing password you set will be automatically encrypted upon submission, and can only be reset or changed by Owners or Developers. Because Owners and Developers can change their Client Sharing password at any point, or turn Client Sharing off, it’s always easy to choose when to make your site editable, and to control who has access to edit it.
Let’s look at how easy Client Sharing is to set up:
We have a few other URL options here, too: Setting a preview URL overrides the link to the live site in the CloudCannon sidebar and header, which is handy for sites with redirects or those hosted externally. Similarly, we can set a custom documentation URL or support URL, the latter of which can also be a
mailto: link. These options are particularly useful to direct clients to contact you if they have any questions.
Now let’s see the site from the user’s perspective:
After navigating to the
/login path on my preview domain and entering my password, I can see that I’m able to create, change and save page and post content, and then publish my changes, but the more complex developer options are hidden from me — no site files, no source code, and no billing options.
If I’m a more non-technical user, that’s probably a good idea!
Client Sharing is particularly helpful when your editors don’t need a permanent profile and CloudCannon account set up. Because the site Owner (typically an agency or freelancer) is in control of the password and can easily reset it, the client editor never needs to worry about forgetting how to access their site. Common users of Client Sharing include:
Because Client Sharing allows user access to editing Pages and Posts and hides Developer settings like Hosting, Builds, and the File Browser, it’s an easy way for a single editor to view a site on CloudCannon and experience the CloudCannon editing interface.
And if it’s important to keep an authorship record of any site changes, you can always add defined Users to your Organization, create a CloudCannon account for them, and set their roles that way — the ‘Editor’ role is functionally the same as that offered by Client Sharing.
When building Jamstack sites for your clients, making their editing experience as simple as possible is vital. And it doesn’t get any easier than sharing a URL and a password with them.
With Client Sharing on CloudCannon, there’ll be no more headaches — for you, or for your clients.
Give your content team full autonomy on your developer-approved tech stack with CloudCannon.
CloudCannon · 1 Jun 2023
David Large · 5 May 2023
CloudCannon · 16 Mar 2023