Skip to main content

Search

Welcome to Support

CMS: How to Lock Pages in Editor 2.0

  • Updated

Overview

Locking is how TeamSideline protects parts of a website (the New Content Builder / Content Editor 2.0) from being changed by the organization's admins in the Site Editor. When an element, section, or page is locked, the admin sees a View Only label in the editor and cannot edit or delete it from the canvas. Locking is intentional, not a bug.

This article explains what is locked by default, why we lock content, and how to handle customer requests to lock, unlock, or hide a page.

What Is Locked by Default

  • Header / Head Navigation. Locked to prevent the Sign-In button and top navigation from being accidentally removed. When selected, the editor shows View Only in the top-right.
  • Footer. Treated as a locked/protected part of the layout so the Admin Sign In link is not removed.
  • System-generated page text. For example, the default text on the registration page ("This page displays all the current registration programs for our league") is system-managed and shows as View Only.

Because these areas are locked, edits to them are performed by the TeamSideline Content/Support team on request — see the examples in "Handling Customer Requests" below.

How to Explain Locked Pages to a Customer

  1. Have the admin open the editor: from the Admin Site Map, go to Content > Site Editor.
  2. Ask them to select the element they cannot change and look for the View Only label (top-right of the editor).
  3. Confirm that View Only means the element/section is locked by design and cannot be edited from the canvas.
  4. Collect the site URL, page name, and a screenshot, then make the change on their behalf or route it to the Content team.

Handling Customer Requests

  • "I can't edit my header/footer." Expected behavior. Make the requested change for them (examples: ticket #204211 header text color, #208354 and #205840 images/widgets stuck in the header, #205333 buttons on division schedule pages).

  • "Please unlock the header so I can edit it." Do not change permissions without confirming policy — see the reviewer question above.

     

Related Need: Hiding a Page Instead of Locking It

Customers often say "lock" when they actually want a page hidden from end users while they work on it. Locking is not the tool for that. Instead:

  • Hide from navigation while editing: go to Content > Configurations > Site Pages and move the page to Standalone Pages so it does not appear in the nav bar; move it back when the page is finished (ticket #175766).
  • Admin-only pages: use Admin Secured Pages, which are accessible only to signed-in admins. See How to Setup Admin Secured Pages.