> For the complete documentation index, see [llms.txt](https://help.steeple.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.steeple.com/en/feeds/feeds-permissions.md). # Feeds permissions The Feeds module uses a permission system to control access to its various features. ## Available permissions * **Add feeds** (`ADD_FEEDS`) : create automatic and manual feeds * **Delete feeds** (`DELETE_FEEDS`) : remove existing feeds * **Rename feeds** (`RENAME_FEEDS`) : modify the title of manual feeds * **Change visibility** (`UPDATE_ORGANIZATION_FEED`) : change the communities that have access to a feed * **Manage webhooks** (`UPDATE_MANUAL_FEED`) : enable/disable webhooks for manual feeds * **Add articles** (`ADD_MANUAL_ARTICLE`) : add articles to a manual feed * **Delete articles** (`DELETE_MANUAL_ARTICLE`) : remove articles from manual feeds * **View statistics** (`VIEW_ARTICLE_VIEWS`) : view article views and readers ## Standard user Collaborators without specific permissions can: * View the feeds they have access to (via their communities) * Read articles * View statistics if the permission is enabled ## Permission assignment Feeds permissions are managed by organization administrators from the Feeds app settings. --- # 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://help.steeple.com/en/feeds/feeds-permissions.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.