Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 00:49:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 143

Improve teams transfer documentation (#7603)

Browse source
This commit is contained in:
Luke Heath 2022-09-07 14:45:15 -05:00 committed by GitHub
parent aafd45fe12
commit f15979a10c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
docs/Using-Fleet/Teams.md
View file

@ -56,7 +56,14 @@ Hosts can only belong to one team in Fleet.
You can add hosts to a new team in Fleet by either enrolling the host with a team's enroll secret or by [transferring the host via the Fleet UI](#transfer-hosts-to-a-team) after the host has been enrolled to Fleet.
To automatically add hosts to a team in Fleet check out the ["Adding hosts" documentation](./Adding-hosts.md#automatically-adding-hosts-to-a-team).
To automatically add hosts to a team in Fleet, check out the ["Adding hosts"
documentation](./Adding-hosts.md#automatically-adding-hosts-to-a-team).
> If a host was previously enrolled using a global enroll secret, changing the host's osquery enroll
> secret will not cause the host to be transferred to the desired team. You must delete the
> `osquery/osquery.db` file on the host, which forces the host to re-enroll
> using the new team enroll secret. Alternatively, you can transfer the host via the Fleet UI, the
> fleetctl CLI using `fleetctl hosts transfer`, or the [transfer host API endpoint](https://fleetdm.com/docs/using-fleet/rest-api#transfer-hosts-to-a-team).
## Transfer hosts to a team