Skip to content

User Guide

This guide is for the people who work in the LyEve admin console: editors who write and publish content, and administrators who manage content types, users and roles. It needs no code. If you run the server, see the Operator guide. If you call the APIs from your own code, see the Developer guide.

Open the console at the address your operator gave you and sign in with your email and password. If you have no account, ask an administrator to create one. Below the form you can choose Forgot password? or Email me a sign-in link, and a Sign in with button appears for each identity provider your instance is set up for. After several failed attempts the form can ask you to complete a captcha.

A new install has no accounts yet. Its console opens a setup page that asks for the setup token and creates the first administrator, as Installation describes.

  1. Core concepts: content types, entries, tenants and roles, the words every screen uses.
  2. Your first content type: define a content type with a relation, preview the change and apply it. The Schema builder in the console does the same.
  3. Creating and editing content: fill in an entry under Content and see what each field type expects.
  4. Drafts, publishing and revisions: publish, schedule, compare two revisions and restore an earlier one.
  5. Media library: upload files, sort them into folders and attach them to entries.
  6. Users, roles and permissions: who may do what, and how to give someone access.
I need to...Read
Add or change a field on a content typeSchema changes
Start from a ready-made content modelSchema presets
Write, save and publish an entryCreating and editing content
Publish at a set time, or undo a changeDrafts, publishing and revisions
Send an entry through review before it goes liveEditorial review
Find entries once there are manySearch and organization
Upload an image and use it in an entryMedia library
Load a spreadsheet of entries at onceBulk import
Create an account or change someone's roleUsers, roles and permissions
Limit a role to some content types or fieldsAccess rules
Give a website its own keyAPI keys
Automate a task without codeFlows
Export or erase one person's dataData protection

A screen appears in the sidebar only while the feature behind it runs for your tenant, and some screens appear only for an admin or a super_admin. Working with entries in the console takes the admin or super_admin role. The editor role writes through the Content API.