From dd6f0795fea3ca10a730bd4cb2f315c03ff2d679 Mon Sep 17 00:00:00 2001 From: Katheryn Satterlee Date: Tue, 5 May 2026 10:50:15 -0400 Subject: [PATCH] Clarify API key requirements for Fleet integration (#44551) Added note about required user role for MDM commands. --- articles/building-webhook-flows-with-fleet-and-tines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/building-webhook-flows-with-fleet-and-tines.md b/articles/building-webhook-flows-with-fleet-and-tines.md index 579f153f61..c5e5e80c4c 100644 --- a/articles/building-webhook-flows-with-fleet-and-tines.md +++ b/articles/building-webhook-flows-with-fleet-and-tines.md @@ -110,7 +110,7 @@ Next, we need to get more details about the device from Fleet. Devices are calle _Tines HTTP Request action to get Fleet device details._ -To access Fleet’s API, we need to provide an API key. We store the API key as a CREDENTIAL in the current story. The API key should belong to an API-only user in Fleet so that the key does not reset when the user logs out. +To access Fleet’s API, we need to provide an API key. We store the API key as a CREDENTIAL in the current story. The API key should belong to an API-only user in Fleet so that the key does not reset when the user logs out. Since we are running MDM commands in this workflow, the user will need a global role of Maintainer or Admin. ![Add credential to Tines story](../website/assets/images/articles/building-webhook-flows-with-fleet-and-tines-3-417x645@2x.png "Add credential to Tines story")