public/grafana
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix relrefs in devloper docs (#51942) (#51995)

Browse Source 
(cherry picked from commit 1c6ee69c2d)

Co-authored-by: Garrett Guillotte <100453168+gguillotte-grafana@users.noreply.github.com>
This commit is contained in:
Grot (@grafanabot)
2022-07-12 01:38:33 +02:00
committed by GitHub
parent 82f7490f7e
commit 4e8cd49e08
18 changed files with 32 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/developers/http_api/org.md
+2 -2
View File
@@ -10,7 +10,7 @@ keywords:
- documentation
- api
- organization
title: 'Organization HTTP API '
title: 'Organization HTTP API'
---
# Organization API
@@ -19,7 +19,7 @@ The Organization HTTP API is divided in two resources, `/api/org` (current organ
and `/api/orgs` (admin organizations). One big difference between these are that
the admin of all organizations API only works with basic authentication, see [Admin Organizations API](#admin-organizations-api) for more information.
> If you are running Grafana Enterprise, for some endpoints you'll need to have specific permissions. Refer to [Role-based access control permissions]({{< relref "../../enterprise/access-control/custom-role-actions-scopes/" >}}) for more information.
> If you are running Grafana Enterprise, for some endpoints you'll need to have specific permissions. Refer to [Role-based access control permissions]({{< relref "../../administration/roles-and-permissions/access-control/custom-role-actions-scopes/" >}}) for more information.
## Current Organization API