Skip to content

Commit fe6144e

Browse files
authored
DOCSP-11560: [mongocli] Clarify API Key role on requirements page (#191)
1 parent 2c17dcf commit fe6144e

File tree

1 file changed

+15
-4
lines changed

1 file changed

+15
-4
lines changed

source/configure.txt

Lines changed: 15 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -30,10 +30,21 @@ command, the {+mcli+} creates a :ref:`configuration file
3030
Prerequisites
3131
-------------
3232

33-
To configure the {+mcli+}, you must have or generate a |svc-api-key| for
34-
your MongoDB service. You must grant the |svc-api-key| the
35-
``Project Owner`` role and add your |ipaddr| or |cidr| block to
36-
the |api| whitelist. To learn more about generating a |svc-api-key| for
33+
To configure the {+mcli+}:
34+
35+
- Add your |ipaddr| or |cidr| block to the |api| whitelist for your
36+
MongoDB service.
37+
- Generate a |svc-api-key| if you don't already have one.
38+
39+
.. note::
40+
41+
|svc-api-key|\s are role-based. Different roles have different
42+
privileges and capabilities, and some {+mcli+} commands are available
43+
to some roles but not others. Be sure that the roles assisgned to
44+
your |svc-api-key| are appropriate for the commands you intend to
45+
use.
46+
47+
To learn more about generating a |svc-api-key| for
3748
your MongoDB service, see the following documentation:
3849

3950
- :atlas:`Atlas API Access </configure-api-access>`

0 commit comments

Comments
 (0)