Skip to content
Snippets Groups Projects
Unverified Commit 8844f1e0 authored by Nemanja Glumac's avatar Nemanja Glumac Committed by GitHub
Browse files

Fix wording in 05-permissions doc (#15162)

parent ca3064b5
Branches
Tags
No related merge requests found
......@@ -65,7 +65,7 @@ If you select `Limit access` for one of your databases, your view will change to
Data access levels for schemas follows the same pattern as for databases:
- **Unrestricted access:** can all tables in this schema, including any tables that might get added in the future.
- **Unrestricted access:** can access all tables in this schema, including any tables that might get added in the future.
- **Limited access:** can only access the tables that you explicitly select.
- **No access:** can’t access any tables in this schema.
......@@ -74,7 +74,7 @@ Lastly, data access levels for tables are almost exactly the same as well:
- **Unrestricted access:** can ask questions about this table and see saved questions and dashboard cards using this table.
- **No access:** can’t ask questions about this table or see saved questions or dashboard cards using this table.
_Note: you’ll notice that tables don’t have the option for limited access. If need to set column-level or row-level data permissions, check out the [data sandboxing](https://www.metabase.com/docs/latest/enterprise-guide/data-sandboxes.html) feature of the [Enterprise Edition](https://www.metabase.com/enterprise/)._
_Note: you’ll notice that tables don’t have the option for limited access. If you need to set column-level or row-level data permissions, check out the [data sandboxing](https://www.metabase.com/docs/latest/enterprise-guide/data-sandboxes.html) feature of the [Enterprise Edition](https://www.metabase.com/enterprise/)._
### A note about Pulses
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment