Aura CMS Security tab with guest view and submit rules
CMS security

Appifio Creator · Lesson AS11 · Intermediate · Aura series · CMS

Content security settings
who can view / append

Adjust in the CMS UI: guests only send contacts; hide drafts; some actions are admin-only.

Learning goals: Find Settings for view/append rights; set everyday rules; test as guest vs admin.

Previous: AS07-AS09 · Next: AS12 · ~12 minutes

Settings Security Save

1. Mental model

Aura CMS Website settings for brand, contact form, and public behavior
Website settings
For each content type (posts / contacts / orders…)
Who may view? · Who may append? · Who may edit/delete?
Safe example: Guest may only append Contacts · may only view Published posts

2. Glossary

TermMeaningWhere you see it
GuestNot logged into adminPublic site
Security settingsScreen choosing who may view/appendCMS → Settings

3. Steps (UI only)

  1. CMS → Settings → find the area for content permissions / security (labels may be “Security”, “Permissions”, “Site mode”… depending on version).
  2. Set: guests may append contacts; may not view drafts; may not edit someone else’s order.
  3. Click Save on that screen.
  4. Test: private/incognito window (guest) vs a window logged into CMS.
Follow on-screen labels only. You do not need (and should not hunt for) technical function names in panel code.

4. Comparisons

  • WordPress members / roles: who sees a private post.
  • Firebase Security Rules: same “who may read/write” idea - Appifio configures it in the UI.

5. Limits & security

  • After you tighten rights, some actions on the live site may be blocked - that is intended.
  • Do not ask AI to “bypass protection” so guests can do dangerous things.

6. Common issues

SituationFix
Contact form blocked / deniedAllow guests to append Contacts
Guests see draftsTighten view rights + post status

7. Checklist

  1. Did you test in an incognito window?
  2. Are drafts hidden from guests?

AS12 - CMS theme & menu in the UI

Appifio Creator · Aura series · AS11