You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clarify reader/writer role descriptions in docs (#4)
Update capabilities table in rbac.mdx and teams.mdx to specify that
roles affect context index permissions, not plan access. Add note
clarifying all team members can read and write plans regardless of role.
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: Matt Dailey <matt@ref.tools>
| Writer | Search context index and add content to index |
14
+
| Reader | Search context index |
15
+
16
+
> All team members can read and write plans regardless of role. Reader and Writer roles only affect permissions for the shared context index (indexed repositories).
15
17
16
18
## Management
17
19
18
20
Roles can be managed from [ref.tools/team](https://ref.tools/team). Make sure that your team is selected in the workspace picker in the top-left of the page.
19
21
20
22
## How to only use public docs
21
23
22
-
Some teams use Ref to only search public documentation sources. The best way to manage this is have one user sign up as an `admin` and invite the rest of the users as `readers`. Then no one will be able to index private sources.
24
+
Some teams use Ref to only search public documentation sources. The best way to manage this is have one user sign up as an `admin` and invite the rest of the users as `readers`. Then no one will be able to index private sources.
| Writer | Search context index and add content to index |
28
+
| Reader | Search context index |
29
+
30
+
> All team members can read and write plans regardless of role. Reader and Writer roles only affect permissions for the shared context index (indexed repositories).
0 commit comments