Skip to content

Users, settings and email

This page is for whoever looks after a DragonslairCMS site: who can do what, the site’s settings, and the emails it sends.

The people who run the site are users, and each has one of three roles:

Role Can
Editor Write and save pages and articles; manage categories, series, tags, people and media; approve, reject and reply to comments; mark corrections done; revert a page or article to its published version. Editors can’t publish or delete pages and articles, or delete comments and corrections: a publisher has to do that.
Publisher Everything an editor can, plus publish, unpublish, schedule and delete pages and articles; delete comments, replies and corrections; change the site’s design (Branding, Palette, Emoticons, Fonts, Navigation, Footer); and change Settings (except the Site URL).
Admin Everything, including managing users and readers, the Site URL, Email templates, and uploading SVG and HTML files.

Readers (visitors with reader accounts) aren’t users and can’t open the admin.

Only admins can manage users. Open Users (under System) and select New user:

  1. Enter their Name and Email. They log in with the email.
  2. Choose a Role.
  3. Leave Active — can sign in ticked.
  4. A strong Password is filled in for you. Copy it before you save, or type your own of at least 12 characters.
  5. Select Create user.

The site doesn’t email new users, so send them the address of the admin (/admin on your site), their email and the password yourself, somewhere private.

Select Edit beside a user to change their name, email or role. To change their password, type a new one in Reset password (leave it empty to keep the current one). Select Save user. A new password logs them out everywhere they’re logged in.

To stop someone logging in without deleting them, untick Active — can sign in. That logs them out straight away, and ticking it again later doesn’t bring their old sessions back. To remove them for good, select Delete. What they did stays in the activity log under their name.

To keep a site from being locked out:

  • You can’t change your own role, deactivate yourself, or delete yourself.
  • You can’t demote, deactivate or delete the only active admin. Make someone else an admin first.

Select Logs beside a user to see everything they’ve done.

There’s no separate screen for changing your own password. Admins can edit themselves in Users and type a new one in Reset password. Changing your own email address or password also needs Your current password; if it’s wrong, nothing is changed. A new password logs you out everywhere else, but you stay logged in where you are. Editors and publishers can ask an admin to do it, or, if the site sends email, use Forgot your password? on the login page.

Everything the admin team does is recorded: logging in, creating, saving, publishing and deleting pages and articles, uploads, setting changes, moderation and more. The Dashboard shows the whole team’s recent activity; Logs on a user shows just theirs. Scheduled articles that publish themselves are recorded as Scheduler.

Times in the admin are shown in UTC.

Long lists in the admin show 20 items a page. Use the Per page menu under a list to show 50 or 100 instead, for as long as you page through that list.

Settings needs the publisher or admin role, and only admins can change the Site URL (canonical). Open Settings (under System), make your changes, and select Save settings at the bottom.

  • Organisation name: shown in the header, the footer, the admin and page titles.
  • Tagline: a short line on the home page and in the footer.
  • Site URL (canonical): the site’s public address, such as https://example.com, with nothing after the name. It must start https://. The RSS feed, the sitemap and every link in the site’s emails use it, and the site sends no email until it’s set. Only an admin can change it, because it decides where password-reset links point; publishers see it but can’t edit it.
  • Email “From” address: the address the site’s emails come from, for example My Site <hello@example.com>. It has to be one address that whoever installed the site has set up for sending. The site sends no email without it.
  • Logo / favicon image: shown at the top left of the site and admin, and as the browser tab icon. A square SVG or PNG works best. It starts as the DragonslairCMS icon.
  • SEO title template: how page titles are put together, with %s standing for the page’s own title, for example %s | My Site. Leave it empty for “Page title — Organisation name”.
  • Default SEO description: used by pages and articles that don’t have a description of their own.
  • Default share image URL: the picture shown when a link to the site is shared, for pages without their own.

Home page chooses what the front page shows: your Static “home” page or the Article feed (blog). See The home page.

Default gallery layout: whether new galleries in articles start as a Grid or a Carousel. Each gallery can still be changed.

Send outgoing email: see Running without email.

  • Allow reader self-registration: whether visitors can create reader accounts. When it’s off, the registration page says Registration is closed. Existing readers can still log in.
  • New registrations require approval: new readers can’t log in until an admin approves them in Readers. When the site isn’t sending email, every new reader waits for approval whatever this says.

Enable the “Suggest a correction” form: when it’s off, the form disappears from every page and article, and the setting on each one is greyed out.

Every email the site sends has a template you can change. Only admins can, because the templates hold the words around password-reset and confirmation links. Open Email templates (under System) to see them all, with their subjects, and whether each one is Default or Customised:

Template Sent
verify_email To a new reader, with the link to confirm their email address
account_approved To a reader whose account is approved
account_rejected To a reader whose account isn’t approved
reset_password To anyone who asks to reset their password
new_article To subscribers, when an article is first published
comment_reply To a reader, when someone replies to their comment
comment_moderated To a reader, when their comment is approved or rejected
admin_new_registration To admins, when a reader registers or verifies their email
admin_new_comment To the admin team, when a comment or reply is posted
admin_new_correction To the admin team, when a correction is suggested

Select a template to change its Subject and Body. Words in double braces, such as {{site_name}} or {{link}}, are filled in when the email is sent; the page lists the ones each template can use. They’re filled in as plain text, so a reader’s comment or username can’t add links or formatting to an email. The Body (HTML) is HTML, so keep the tags like <p> and <a href="{{link}}"> in place, and wrap each paragraph in <p>…</p>: line breaks on their own don’t show. A plain-text version is made for you automatically. Select Save template. Reset to default puts back the original.

Every active user gets the three admin_ emails. There’s currently no way to turn them off for one person.

Sending email needs extra setup by whoever installed the site (a paid Cloudflare plan and a domain set up for email), plus a Site URL and an Email “From” address in Settings. Without it, turn Send outgoing email off in Settings. The site then works without email (as it also does while the Site URL or From address is empty), and adapts so nobody gets stuck:

  • You find out about new comments, corrections and readers from the numbers in the sidebar and on the Dashboard, instead of by email.
  • Readers register without confirming their email. Every new account waits in Readers for an admin to approve it, even if New registrations require approval is off, because there’s no other check on who they are.
  • Password resets by email are switched off, and the Forgot your password? links disappear. Admins reset each other’s passwords in Users, and readers’ passwords in Readers with Set password.
  • Readers aren’t emailed about new articles, replies or moderation.

If sending ever fails, the site carries on regardless; the email just isn’t sent.