> For the complete documentation index, see [llms.txt](https://docs.subsalt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.subsalt.io/administration/access-control-and-sharing.md).

# Access control and sharing

Subsalt provides multiple ways for administrators to configure granular access to various databases, tables, and views of the application.

## Database access

Database access can be provided to registered users via **Databases >&#x20;*****\[your database]*****&#x20;> Permissions > Grant Access.** Depending on the role granted, the user(s) may be also need to be explicitly granted access to the tables/views associated with the database.

### Table/view access

Explicit table and view access may be granted or revoked for users. This may be done via ***\[your database] > Permissions > \[your user(s)] > Edit access***.&#x20;

## Roles

<table><thead><tr><th width="131.14373779296875">Role</th><th>Description</th></tr></thead><tbody><tr><td><strong>Guest</strong></td><td>A user with no access to databases by default. Access to databases and associated tables and views must be explicitly granted.</td></tr><tr><td><strong>User</strong></td><td>A user with <strong>read-only</strong> access to all databases by default as well as associated tables and views.</td></tr><tr><td><strong>Administrator</strong></td><td>A user that has <strong>read</strong> and <strong>write</strong> access to all databases by default and associated tables and views. Administrators can create and manage databases as well users.</td></tr></tbody></table>


---

# 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.subsalt.io/administration/access-control-and-sharing.md?ask=<question>&goal=<user_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.
