# Hasura Roles ### Three Initial Roles A0s requested in [this document](https://docs.google.com/spreadsheets/d/1gNCz63qFpztiuL_JK4aPNnicjCglmATOW1dbpU0wxWk/edit#gid=351804243), there are currently three roles implemented in production: * `moped-admin` This role can create a `moped-editor` as well as read-write access to any part of the database. No deletions are permitted, aggregations are not allowed either. * `moped-editor` This role has read-write access to any part of the database. No deletions are permitted, aggregations are not allowed either. * `moped-viewer` This role has read-only access to any part of the database. ### How are these roles implemented? The rules are implemented through a Hasura metadata migration. First, the local hasura cluster is started, then the console. While the console is open, the permissions are changed, then the console will make changes to the metadata file. ### How can these roles be changed? First, create a new branch in git. Then, start the cluster (locally), and open the hasura console. Once the console is open, go to any table you need to make changes to, then change the permission settings for the specific role you need to change. Once you make changes, the console will directly make changes to the metadata file, which is tracked by git, meaning that git will show differences in the code which you can commit and push to your branch, those changes made to your PR can be tested by someone else without affecting staging and prod, and once approved the branch will be merged to staging (or production) and the migration will be applied automatically by GitHub actions. --- # 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://atd-dts.gitbook.io/moped-documentation/dev-guides/hasura/hasura-roles.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.