Skip to content

Commit e50345c

Browse files
authored
Merge pull request #6164 from stsewd/update-sharing-docs
Update docs for sharing
2 parents 1568dfb + 9b61db5 commit e50345c

File tree

1 file changed

+29
-6
lines changed

1 file changed

+29
-6
lines changed

docs/commercial/sharing.rst

Lines changed: 29 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,30 +2,42 @@ Sharing
22
-------
33

44
.. note::
5-
This feature only exists on `Read the Docs for Business <https://readthedocs.com/>`_.
65

7-
You can share your project with users outside of your company.
8-
There are two ways to do this:
6+
This feature only exists on `Read the Docs for Business <https://readthedocs.com/>`__.
7+
8+
You can share your project with users outside of your company:
99

1010
* by sending them a *secret link*,
1111
* by giving them a *password*.
1212

1313
These methods will allow them to view a specific project inside your company.
1414

15+
Additionally, you can use a HTTP Authorization Header.
16+
This is useful to have access from a script.
17+
1518
Enabling
1619
~~~~~~~~
1720

1821
* Go into your *Project Admin* page and to the *Sharing* menu.
19-
* Under the *Share with someone new* heading, select the way you prefer (secret link or password), add an expiration date and a *Description* so you remember who you're sharing it with.
22+
* Under the *Share with someone new* heading, select the way you prefer (secret link, password, or HTTP header token),
23+
add an expiration date and a *Description* so you remember who you're sharing it with.
2024
* Click *Share!* to create.
2125
* Get the info needed to share your documentation with other users:
2226

2327
* If you have selected secret link, copy the link that is generated
2428
* In case of password, copy the link and password
29+
* For HTTP header token, you need to pass the ``Authorization`` header in your HTTP request.
2530

2631
* Give that information to the person who you want to give access.
2732

28-
.. note:: You can always revoke access in the same panel.
33+
.. note::
34+
35+
You can always revoke access in the same panel.
36+
37+
.. note::
38+
39+
Sharing using a password and a HTTP header token are currently in beta.
40+
If you want access to these features, email us to [email protected].
2941

3042
Effects
3143
~~~~~~~
@@ -40,6 +52,17 @@ Password
4052
********
4153

4254
Once the person you send the link to clicks on the link, they will see
43-
a *Authorization required* page asking them for the password you
55+
an *Authorization required* page asking them for the password you
4456
generated. When the user enters the password, they will have access to
4557
view your project.
58+
59+
HTTP Authorization Header
60+
*************************
61+
62+
You need to send the ``Authorization`` header with the token on each HTTP request.
63+
The header has the form ``Authorization: Token <ACCESS_TOKEN>``.
64+
For example:
65+
66+
.. prompt:: bash $
67+
68+
curl -H "Authorization: Token 19okmz5k0i6yk17jp70jlnv91v" https://docs.example.com/en/latest/example.html

0 commit comments

Comments
 (0)