Skip to content

Commit 4c8a35f

Browse files
committed
Note that RTD for Business does ask for write permissions
1 parent 1731439 commit 4c8a35f

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

docs/connected-accounts.rst

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,8 @@ that allows us to read information about and clone your repositories.
2323
Permissions for connected accounts
2424
----------------------------------
2525

26-
Read the Docs does **not** ask for write permission to your repositories' code
26+
Read the Docs does not generally ask for write permission to your repositories' code
27+
(with one exception detailed below)
2728
and since we only connect to public repositories we don't need special permissions to read them.
2829
However, we do need permissions for authorizing your account
2930
so that you can login to Read the Docs with your connected account credentials
@@ -61,6 +62,10 @@ Repository status (``repo:status``)
6162
:doc:`Read the Docs for Business </commercial/index>`
6263
asks for one additional permission (``repo``) to allow access to private repositories
6364
and to allow us to setup SSH keys to clone your private repositories.
65+
Unfortunately, this is the permission for read/write control of the repository
66+
but there isn't a more granular permission
67+
that only allows setting up SSH keys for read access.
68+
6469

6570
Bitbucket
6671
~~~~~~~~~

0 commit comments

Comments
 (0)