> 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/administration/roles-et-permissions.md). # Employee roles and permissions ### The two Steeple roles Steeple distinguishes two main roles: * **Administrator** : full access to the organization’s administration (management of employees, communities, applications, TV screens, settings, etc.) * **Member** : access to the app’s features (posts, messaging, directory, events, etc.) without access to administration ### What each role can do #### Administrator * Manage employees (add, edit, suspend, remove) * Manage communities and their members * Manage applications (hide/show) * Manage TV screens * Access organization statistics and settings * Everything a member can do #### Member * Post in the communities they belong to * View the directory and profiles * Use messaging * Access visible applications (News, Jobs, Docs, Events) ### Change an employee’s role 1. Go to **Administration** > **Employees** (`/administration/users`) 2. Search for and click the relevant employee. 3. Click on **Edit**. 4. Edit the **Role** field (administrator or member). 5. Save the changes. #### Single-community case If the organization has only one community, the role applies globally: #### Case of multiple communities With multiple communities, the role can be different for each community (for example: administrator in the Commerce community, member in the others). #### Administrator role on the main and dynamic communities The administrator role can be given on **all types of communities** : the main one, manual communities, and dynamic communities. For the main community and dynamic communities, members are **managed automatically** by Steeple. The administrator role is then tied to the employee’s presence in the community: * If the employee leaves the community (for example following a change of department or site that removes them from a dynamic community), their administrator role is automatically removed. * If you want to give it back later, you will need to reassign it manually. ### Important restriction There must always be **at least one administrator** in the organization. It is impossible to remove administrator rights from the last remaining administrator. --- # 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/administration/roles-et-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.