docs: clarify Editor role (#625)

* docs: clarify Editor role * Update docs/infracost_cloud/key_concepts.md --------- Co-authored-by: Vadim Golub <[email protected]>
infracost · Apr 2, 2024 · f6900c8 · f6900c8
1 parent 39557d4
commit f6900c8
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/infracost_cloud/key_concepts.md b/docs/infracost_cloud/key_concepts.md
@@ -44,7 +44,7 @@ Infracost API keys are associated with organizations and can be retrieved from t
 From the Members page, you can invite your team members to join your organization. Currently these roles are supported:
 - **Org Owner**: they have complete control over the organization. We recommend giving the main billing contact the owner role. From the Members page, the owner can transfer this role to another member. Only the owner can delete the organization or change its name or slug.
 - **Org Admin**: they can do everything except deleting the organization, or changing its name or slug. We recommend giving FinOps/Platform team members the admin role so they can setup integrations for everyone, manage custom price books, and configure other Org Settings.
-- **Org Editor**: they can change everything except Org Settings and data exports. This means they cannot invite members to the organization either. We recommend giving team leads/managers the editor role so they can also add guardrails, policies and reports for their teams if required.
+- **Org Editor**: they can change everything except Org Settings and data exports. This means they cannot invite members to the organization either. They can view everything except the following Org Settings: API keys, Members, Plan and billing, Custom price books, Integrations. We recommend giving team leads/managers the editor role so they can also add guardrails, policies and reports for their teams if required.
 - **Org Viewer**: they can view everything except the following Org Settings: API keys, Members, Plan and billing, Custom price books, Integrations. They cannot make any changes apart from their personal user settings such as their password or multi-factor-authentication setup. We recommend giving engineers the viewer role so they can see preexisting issues and fix them.
 
 ## Repos