-`X-Hasura-User-Id`: this variable usually denotes the user executing the request.
-`X-Hasura-Role`: This variable denotes the role with which the user is executing the current request. Hasura has a built-in notion of a role, and will explicitly look for this variable to infer the role.
In our database we have several roles which are simple arbitrary names.
Each role can be given a set of permissions and actions (`select`, `insert`, `update`, `delete`). That will execute against each table of the database.
This is the same as saying : if the value of the `user_id` column equals the value of the session variable `X-Hasura-User-Id`, it allows this request to execute on the current row and get information on that user id.
-`audit`, the user only can query this table if the user id from the `X-Hasura-User-Id` variable is equal to one of the `members`, or the `auditorId`.
-`result`, the user only can query this table if the `X-Hasura-User-Id` is equal to the `userId` or one of the members from their group.
-`transaction`, this table can be queried by users if the `X-Hasura-User-Id` is equal to the `userId`.
-`record`, the same applies to this table and the tables below.
-`progress`
-`user_role`
-`user`, the same applies to this table but with the `id`.
- _`user_role_view`_
- _`audit_private`_
- _`progress_by_path_view`_
- _`progress_view`_
- _`xp`_
- _`xp_by_event`_
- _`xp_by_path`_
---
-`campus-admin` : this role allows users to query every table, but with the variables `X-Hasura-campus` checked (campus check). This means that users with this role will only be able to query information from their own campus. Example: a user in campus `madere` can only query the content associated to that campus. The following tables can be queried:
-`select` action:
- without permission rules:
-`group_status`
-`object_status`
-`object_type`
-`result_type`
-`role`
-`transaction_type`
-`user_role`
- _`user_public_view`_
- _`user_role_view`_
- with permission rules:
-`event_user`
-`audit`
-`group`
-`group_user`
-`match`
-`object`
-`event`
-`progress`
-`record`
-`registration`
-`registration_user`
-`result`
-`transaction`
-`user`
- _`progress_by_path_view`_
- _`audit_private`_
- _`event_user_view`_
- _`event_with_results_ready_view`_
- _`progress_view`_
- _`registration_user_view`_
- _`registration_with_event_ready_view`_
- _`toad_result_view`_
- _`xp_by_event`_
- _`xp_by_path`_
---
-`campus-admin-read-only` : this role allows users to query almost all tables (only using the `select` action). But with the same permission rule in the `campus-admin`. The following tables can be queried:
- without permission rules:
-`group_status`
-`object_status`
-`object_type`
-`result_type`
-`role`
-`transaction_type`
-`user_role`
- _`user_public_view`_
- _`user_role_view`_
- with permission rules:
-`event_user`
-`audit`
-`group`
-`group_user`
-`match`
-`object`
-`event`
-`progress`
-`record`
-`registration`
-`registration_user`
-`result`
-`transaction`
-`user`
- _`progress_by_path_view`_
- _`audit_private`_
- _`event_user_view`_
- _`event_with_results_ready_view`_
- _`progress_view`_
- _`registration_user_view`_
- _`registration_with_event_ready_view`_
- _`toad_result_view`_
- _`xp_by_event`_
- _`xp_by_path`_
---
-`admin-read-only` : this role allows users to query all tables only using the `select` action.
---
-`admin` : this role allows users to query using any action in any table on the database.
> You can see more about each role by going to the [graphiql](https://((DOMAIN))/graphiql) in the docs section. Note that you must be logged in with the user role you desire to see. For the role `anonymous` you do not need to be logged in. If you want to see the possible tables that can be queried by an admin, you must login with an admin, and so on...