Signing in

Every Core dna site has its admin at /cdna-admin on the site's own address, for example https://www.example.com/cdna-admin; a development or staging environment has it at the same path on its own address. Sign in with the account your administrator created for you. Sign in to Core dna covers password resets, and Single Sign On (SSO) signing in with your organisation's account.

How the admin is organised

After signing in you see the dashboard. The navigation on the left lists the modules, grouped by what you are working on, and the sections of this documentation follow the same groups:

  • Content: pages, blogs, FAQs, books, menus and files, with the categories, tags and global components they share.
  • Automations: jobs (formerly hooks) and the scheduler.
  • Customization: layouts, custom fields, input types and custom entities, the building blocks content is poured into.
  • Transactions: products and the rest of commerce.
  • Interactions: forms, the mailer and chat channels.
  • AI Agents: agents that review your content and propose changes for you to accept.
  • Accounts: users, groups and permissions.
  • System: sites, rewrites, utilities, the audit log and global settings.

What you can open depends on your permissions, so if a section you need is missing, ask your administrator.

The question mark at the top right opens this documentation, and the small help icons beside many fields explain them when you hover over them.

The screens you will use most

  • A list of one kind of record, with search and filters. Pages are listed as a tree, and you reorder them by dragging.
  • The edit screen of one record. For a page it has five tabs: Content (the title, the layout and its areas), Details (owner, slug, parent, tags, categories), SEO, Permissions and Attributes.
  • The versions of a record, at the top right of the edit screen: every saved version, which you can view, compare with the current one, or make active again. See Versioning.

Saving is not publishing

Saving stores your changes as a version. Whether visitors see them depends on two more things: that the version is the active one, and that the record is published. Previewing and publishing explains both, and why it is safe to save often.