-
What Grafana version and what operating system are you using?
Grafana OSS v12.4 
Grafana OSS v13.0
-
What are you trying to achieve?
restrict access to DataSources
-
How are you trying to achieve it?
In v12.x we are restricting our internal teams access to different datasources by placing groups of users in different orgs.
-
What happened?
It looks like we can’t create or manage orgs in v13 
Are Orgs really depreciated in v13? It’s not listed in the Breaking Changes page.
What are other people doing here?
Can anyone advise here on what the best practice now is for OSS?
Orgs are not deprecated in Grafana v13. The Organization HTTP API still exists and legacy APIs remain fully accessible. So your existing org-based approach still works.
If you can’t create or manage orgs in v13, it is likely a permissions issue. Creating, editing and deleting organizations requires Grafana Server Administrator permissions not just Org Admin. Check under Administration → Users and confirm your account has the Server Admin flag enabled.
Datasource permissions to restrict access to specific users, teams, or roles isonly available in Grafana Enterprise or Grafana Cloud not OSS.
For Grafana OSS options are:
Keep using multiple orgs → still works in v13, confirm Server Admin access
Separate Grafana instances per team → clean isolation, more operational overhead
Upgrade to Grafana Enterprise → proper datasource-level permissions without multiple orgs
