# Membership & Roles Manage who has access to your Rova Web workspace and what they can do. ## Role Definitions | Role | Ideal for... | | ---------- | ----------------------------------------------------------------------------- | | **Owner** | The person responsible for the Rova account and billing. | | **Admin** | Team leads or DevOps engineers who need to manage infrastructure and members. | | **Editor** | QA engineers and developers who write and maintain tests. | | **Viewer** | Stakeholders (Product Managers, Designers) who only need to review results. | ## Managing Members ### Adding Members Invite members via email. If they don't have a Rova account yet, they will be prompted to create one. ### Changing Roles Owners and Admins can update a member's role at any time from the **Members** list. Changes take effect immediately. ### Removing Members When a member leaves the team, remove them from the workspace to revoke their access to tests, API keys, and project data. ## Recommendations * **Minimize Owners**: Keep the number of Owners small (usually 1-2 people). * **Default to Editor**: Most technical team members should be Editors. * **Use Viewers for external partners**: If you work with an agency or external stakeholders, the Viewer role is the safest way to share progress. --- # Agent Instructions: 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: ``` GET https://docs.rova.qa/rova-web/workspace/membership.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.