> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-pages/media-and-content/editing-permission-and-lock-edits.md).
# Editing Permission and Lock Edits
To prevent colleagues from making unwanted changes and have greater control over who and what edits others in your team can make to the live pages, stories and templates you've created, Maker lets you assign editing permission. As an admin, you can provide editing permissions based on the various roles assigned to the team members.
(To learn more about team roles, visit this page .)
To lock (or unlock) edits, you must have admin permissions or be the author (user creating the story) of the story. Click on the cog wheel icon on the top right of the editor and select "Editing Permission".
Editing Permission for Story
Editing Permissions for Templates
You can view and change permissions on the Editing Permissions dialog for a story and on the templates panel for the templates you have saved. By default all stories and templates are unlocked, however, users can change permissions of the story anytime by selected from the choices given - lock, lock all edits or lock design edits and selecting " Apply or Save ".
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.maker.co/maker-pages/media-and-content/editing-permission-and-lock-edits.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.