Signing in
The admin for any Core dna site lives under /cdna-admin on that site's own hostname. For this documentation hub that is hub.coredna.com/cdna-admin; a development or staging environment uses the same path on its own hostname.
Sign in with the account your administrator created for you. Accounts are per-client, so the same login works across the sites you have been granted access to — but what you can see and change is controlled per site.
How the admin is organised
The admin is grouped by what you are editing rather than by where it appears on the site:
- Content — the records that make up the site: pages, books, blog posts, FAQs.
- Files — images and documents, in folders.
- Customization — layouts, components, input types and menus. This is where the building blocks live, as opposed to the content poured into them.
- Settings — site configuration, users and permissions.
If you cannot find a section, it is usually a permissions matter rather than a missing feature — the navigation only shows what your account is allowed to open.
The screens you will actually use
Day to day, most editing happens in three places:
- A content list — every record of one type, with search and filters. This is where you create, duplicate, publish and delete.
- A record editor — one record's fields. What you see here is decided by the record's layout: the layout declares a set of named areas, and each area appears as a field.
- The revision history — every saved version of a record, with the ability to compare two of them and to make an older one active again.
A note on saving
Saving a record does not publish it. Saving creates a new revision; publishing is a separate action that decides whether visitors can see it. It is safe to save often — you are never overwriting the version that is live.