[mintlify]

Applies the open review findings from #505, #506 and #507: the roles page now uses the Settings > User Management label, the tags page covers controls (beta) and reading tags with the CLI, and the service accounts page covers listing and revoking keys.

Based on #505, #506 and #507.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
kosli	🟢 Ready	View Preview	Nov 7, 2026, 10:13 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

[claude]

Claude finished @mintlify[bot]'s task in 51s —— View job

---

Doc review: PR #511

I checked the changed lines against the generated reference pages (kosli_list_api-keys, kosli_delete_api-key, kosli_tag, kosli_get_*, terraform-reference/resources/control). All the new internal link targets exist, and membership_audit_log is in navigation. The service-accounts claims match the CLI reference: metadata only, never the key value, and deleting a key also deletes the keys created with it. Nothing else from the Settings > Members label is left anywhere on the site.

administration/managing_tags.md

Improvement: control tagging is announced but not shown in "Tag resources"

• Location: administration/managing_tags.md:65 and :67-87

• Issue: The intro, the resource table and the Terraform sentence on line 35 now say controls can be tagged. The section that shows how to do it still covers only flows, environments and repos:

  • The Terraform tab's "full schema" line (65) links only kosli_environment and kosli_flow.
  • The CLI tab has no kosli tag control example.

  A reader who wants to tag a control has to work it out from the reference.

• Recommendation:

  • Add kosli_control resource to line 65.
  • Add a CLI example such as kosli tag control <CONTROL-IDENTIFIER> --set team=platform. tutorials/working_with_controls.mdx:113 already uses this form.

• Fix this →

Suggestion: kosli get env is not a documented command name (:186, see the inline comment). Use kosli get environment and link the three get reference pages.

---

1 Improvement, 1 Suggestion, no Critical findings. This review is advisory. Neither finding blocks the merge.

[claude]

Suggestion: The published command is kosli get environment (reference). An env alias may exist for get, but nothing in the generated reference confirms it. kosli tag env is confirmed only because kosli tag lists it as a resource type. Using the documented name, with links, is safer:

Suggested change

	`kosli get flow`, `kosli get env`, and `kosli get control` show tags the same way. [`kosli list repos`](/client_reference/kosli_list_repos) has a `TAGS` column.
	[`kosli get flow`](/client_reference/kosli_get_flow), [`kosli get environment`](/client_reference/kosli_get_environment), and [`kosli get control`](/client_reference/kosli_get_control) show tags the same way. [`kosli list repos`](/client_reference/kosli_list_repos) has a `TAGS` column.