> For the complete documentation index, see [llms.txt](https://docs.brava.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brava.finance/platform/workspace-permissions.md). # Workspace Permissions Who may propose, approve, and sign within a workspace. ## Workspace Permissions Who may propose, who may approve, and who may sign are three separate questions. ### Roles | Role | Can | | ---------- | ------------------------------------------------------------------- | | **Owner** | Everything, including managing members and the custodian connection | | **Editor** | Build and edit strategies, and execute transactions | | **Viewer** | See everything. Change nothing | Members are invited per workspace. A person may be an Owner of one and a Viewer of another. ### What a role does not grant No role signs. Execution requires the wallet the workspace is connected to. An Editor may prepare and submit a transaction, and it still waits on your custodian. Where the connected wallet is not the one the workspace authorises, the action is unavailable and the interface says so rather than failing at signing time. The ability to instruct and the ability to sign are held by different people, on purpose. ### Agents An agent operates inside a **mandate**: what it may propose, and how far. An agent proposes. It does not sign, and it does not hold a role. Its work arrives as a pending action on the Portfolio screen and waits on a person. ### Changing permissions Owners manage members in workspace settings. Removing a member removes their access to that workspace and nothing else. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.brava.finance/platform/workspace-permissions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.