Skip to content
This repository has been archived by the owner on Jan 29, 2024. It is now read-only.

Commit

Permalink
Merge pull request #2221 from aiven/staceys-project-roles-style-guide
Browse files Browse the repository at this point in the history
Align project roles article with style guide
  • Loading branch information
staceysalamon-aiven authored Nov 21, 2023
2 parents fe2dfc2 + 57dc47f commit 0f18fd2
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions docs/platform/reference/project-member-privileges.rst
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,9 @@ You can grant different levels of access to project members using roles:

* **Admin**: Full access to the project and its services.

* Do not have access to organization settings such as billing.
* Are the only users allowed to add more users to the project.
* When you create a project, you automatically have this access level.
* This role is automatically granted to users who create a project.
* Does not have access to organization settings such as billing.
* Can add and remove project members.

.. note::

Expand All @@ -25,8 +25,8 @@ You can grant different levels of access to project members using roles:

* Can make changes to services and databases, for example: creating databases, connecting to databases, removing Aiven for OpenSearch® indexes, creating and modifying Aiven for Apache Kafka® topics, and creating and modifying Aiven for PostgreSQL® connection pools.
* Can create and change service database users.
* Cannot add or change project members.
* Cannot make changes that affect billing like powering services on or off.
* Cannot make changes to the project members.
* Cannot make changes that affect billing (such as powering services on or off).

* **Read-only**: Only allowed to view services.

Expand Down

0 comments on commit 0f18fd2

Please sign in to comment.