From 490b8bf65ab84aafe5af107406e1ea87c741341e Mon Sep 17 00:00:00 2001 From: Marcelo Trylesinski Date: Thu, 14 Nov 2024 10:35:58 +0100 Subject: [PATCH] Fix pipeline --- docs/guides/advanced/using-environments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/advanced/using-environments.md b/docs/guides/advanced/using-environments.md index 0a389d33..91166678 100644 --- a/docs/guides/advanced/using-environments.md +++ b/docs/guides/advanced/using-environments.md @@ -48,5 +48,5 @@ environment name. ## Should I Use Environments or Projects? Environments are more lightweight than projects. Projects give you the ability to assign specific -user groups and permissions levels (see this [organization structure diagram](../../../reference/organization-structure/) for details). +user groups and permissions levels (see this [organization structure diagram](../../reference/organization-structure.md) for details). So if you need to allow different team members to view dev vs. prod traces, then projects would be a better fit.