diff --git a/articles/connect-end-user-to-wifi-with-certificate.md b/articles/connect-end-user-to-wifi-with-certificate.md index 24eec65b99..96d18c79c3 100644 --- a/articles/connect-end-user-to-wifi-with-certificate.md +++ b/articles/connect-end-user-to-wifi-with-certificate.md @@ -31,7 +31,7 @@ To connect end users to Wi-Fi or VPN with DigiCert certificates, we'll do the fo 3. Select your **Business unit** and **Issuing CA**. 4. Select **REST API** from **Enrollment method**. Then select **3rd party app** from the **Authentication method** dropdown and select **Next**. 5. Configure the certificate expiration. At most organizations, this is set to 90 days. -6. In the **Flow options** section, make sure that **Allow dupliate certificates** is checked. +6. In the **Flow options** section, make sure that **Allow duplicate certificates** is checked. 7. In the **Subject DN and SAN fields** section, make sure to add **Common name**. **Other name (UPN)** is optional. For **Common name**, select **REST request** from **Source for the field's value** dropdown and check **Required**. If you use **Other name (UPN)**, select **REST Request** and check both **Required** and **Multiple**. Organizations usually use device's serial number or user's email, you can use Fleet variables in the next section, and Fleet will replace these variables with the actual values before certificate is delivered to a device. 8. Click **Next** and leave all default options. We'll come back to this later. @@ -218,7 +218,7 @@ To connect end users to W-Fi or VPN with a custom SCEP server, we'll do the foll 2. Replace the ``, with name you created in step 3. For example, if the name of the CA is "WIFI_AUTHENTICATION" the variables will look like this: `$FLEET_VAR_CUSTOM_SCEP_PASSWORD_WIFI_AUTHENTICATION` and `FLEET_VAR_CUSTOM_SCEP_DIGICERT_DATA_WIFI_AUTHENTICATION`. -3. If your Wi-Fi or VPN requires certificates that are unique to each host, update the `Subject`. You can use `$FLEET_VAR_HOST_END_USER_EMAIL_IDP` if your hosts automatically enrolled (via ADE) to Fleet with [end user authentication]((https://fleetdm.com/docs/rest-api/rest-api#get-human-device-mapping)) enabled. You can also use any of the [Apple's built-in variables](https://support.apple.com/en-my/guide/deployment/dep04666af94/1/web/1.0). +3. If your Wi-Fi or VPN requires certificates that are unique to each host, update the `Subject`. You can use `$FLEET_VAR_HOST_END_USER_EMAIL_IDP` if your hosts automatically enrolled (via ADE) to Fleet with [end user authentication](https://fleetdm.com/docs/rest-api/rest-api#get-human-device-mapping) enabled. You can also use any of the [Apple's built-in variables](https://support.apple.com/en-my/guide/deployment/dep04666af94/1/web/1.0). 4. In Fleet, head to **Controls > OS settings > Custom settings** and add the configuration profile to deploy certificates to your hosts. diff --git a/articles/deploy-software-packages.md b/articles/deploy-software-packages.md index f63809fd75..78e06c6e45 100644 --- a/articles/deploy-software-packages.md +++ b/articles/deploy-software-packages.md @@ -160,7 +160,7 @@ After a software package is installed on a host, it can be uninstalled on the ho ## Manage packages with Fleet's REST API -Fleet also provides a REST API for managing software programmatically. The API allows you to add, update, retrieve, list, and delete software. Detailed documentation on Fleet's [REST API is available]([https://fleetdm.com/docs/rest-api/rest-api#software](https://fleetdm.com/docs/rest-api/rest-api#software)), including endpoints for installing and uninstalling packages. +Fleet also provides a REST API for managing software programmatically. The API allows you to add, update, retrieve, list, and delete software. Detailed documentation on Fleet's [REST API is available](https://fleetdm.com/docs/rest-api/rest-api#software), including endpoints for installing and uninstalling packages. ## Manage packages with GitOps diff --git a/articles/enforce-disk-encryption.md b/articles/enforce-disk-encryption.md index c692e090ab..56c0dbdcea 100644 --- a/articles/enforce-disk-encryption.md +++ b/articles/enforce-disk-encryption.md @@ -94,7 +94,7 @@ First, in Fleet, head to the host's **Host details** page in Fleet and check it' #### On (automatic) -1. Login to [Microsoft Azure](portal.azure.com) (Entra) and navigate to the **Users** page. +1. Login to [Microsoft Azure](https://portal.azure.com) (Entra) and navigate to the **Users** page. 2. Select the end user's user and select **Reset password**. diff --git a/articles/role-based-access.md b/articles/role-based-access.md index 177d6f48d9..449f718b1d 100644 --- a/articles/role-based-access.md +++ b/articles/role-based-access.md @@ -170,7 +170,7 @@ Users with access to multiple teams can be assigned different roles for each tea | Execute MDM commands on macOS and Windows hosts* | | | ✅ | ✅ | | | View results of MDM commands executed on macOS and Windows hosts* | ✅ | ✅ | ✅ | ✅ | | | Edit [team OS settings](https://fleetdm.com/docs/rest-api/rest-api#os-settings) | | | ✅ | ✅ | ✅ | -| Edit [macOS setup experience]([https://fleetdm.com/docs/](https://fleetdm.com/guides/macos-setup-experience#basic-article))\* | | | ✅ | ✅ | ✅ | +| Edit [macOS setup experience](https://fleetdm.com/guides/macos-setup-experience#macos-setup-assistant)\* | | | ✅ | ✅ | ✅ | | Run scripts on hosts | | | ✅ | ✅ | | | View saved scripts | ✅ | ✅ | ✅ | ✅ | | | Edit/upload saved scripts | | | ✅ | ✅ | | diff --git a/docs/Configuration/agent-configuration.md b/docs/Configuration/agent-configuration.md index a52987755a..c1dcb62118 100644 --- a/docs/Configuration/agent-configuration.md +++ b/docs/Configuration/agent-configuration.md @@ -78,7 +78,7 @@ In the `decorators` key, you can specify queries to include additional informati ### yara -You can use Fleet to configure the `yara` and `yara_events` osquery tables, used to administer [YARA rules]((https://fleetdm.com/guides/remote-yara-rules) for continuous monitoring. +You can use Fleet to configure the `yara` and `yara_events` osquery tables, used to administer [YARA rules](https://fleetdm.com/guides/remote-yara-rules) for continuous monitoring. ## extensions diff --git a/docs/Contributing/architecture/software/vulnerability-management.md b/docs/Contributing/architecture/software/vulnerability-management.md index 4104fce0cc..684fa64d7b 100644 --- a/docs/Contributing/architecture/software/vulnerability-management.md +++ b/docs/Contributing/architecture/software/vulnerability-management.md @@ -32,8 +32,8 @@ To learn more, read our [vulnerability processing](https://fleetdm.com/guides/vu ## Related resources -- [Vulnerability processing guide]((https://fleetdm.com/guides/vulnerability-processing)) -- [Software filtering guide]((https://fleetdm.com/guides/filtering-software-by-vulnerability)) -- [Remediating the cx vulnerability with Fleet guide]((https://fleetdm.com/guides/remediating-the-xz-vulnerability-with-fleet)) +- [Vulnerability processing guide](https://fleetdm.com/guides/vulnerability-processing) +- [Software filtering guide](https://fleetdm.com/guides/filtering-software-by-vulnerability) +- [Remediating the cx vulnerability with Fleet guide](https://fleetdm.com/guides/remediating-the-xz-vulnerability-with-fleet) - [Software Product Group Documentation](../../product-groups/software/) - Documentation for the Software product group -- [Software Development Guides](../../guides/software/) - Guides for Software development \ No newline at end of file +- [Software Development Guides](../../guides/software/) - Guides for Software development diff --git a/handbook/company/product-groups.md b/handbook/company/product-groups.md index 8cc1eb87df..de33dbfa84 100644 --- a/handbook/company/product-groups.md +++ b/handbook/company/product-groups.md @@ -360,7 +360,7 @@ When a release is in testing, QA should use the Slack channel #help-qa to keep e When a critical bug is found, the Fleetie who labels the bug as critical is responsible for following the [critical bug notification process](https://fleetdm.com/handbook/company/product-groups#notify-the-community-about-a-critical-bug) below. -All unreleased bugs are addressed before publishing a release. Released bugs that are not critical may be addressed during the next release per the standard [bug process](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/releasing-fleet.md#bug-process). +All unreleased bugs are addressed before publishing a release. Released bugs that are not critical may be addressed during the next release per the standard [bug process](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/workflows/releasing-fleet.md#bug-process). - **Release blockers:** Product may add the `~release blocker` label to user stories to indicate that the story must be completed to publish the next version of Fleet. Bugs are never labeled as release blockers. @@ -383,7 +383,7 @@ Once the critical bug is confirmed, a [priority label](https://fleetdm.com/handb The relevant release page on GitHub is updated to indicate that the release contains a critical bug, as shown on the [fleet-v4.45.0 release page](https://github.com/fleetdm/fleet/releases/tag/fleet-v4.45.0). -When a critical bug is identified, we will then follow the patch release process in [our documentation](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/releasing-fleet.md#patch-releases). +When a critical bug is identified, we will then follow the patch release process in [our documentation](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/workflows/releasing-fleet.md#prepare-a-patch-release). > After a critical bug is fixed, [an incident postmortem](https://fleetdm.com/handbook/engineering#perform-an-incident-postmortem) is scheduled by the EM of the product group that fixed the bug. diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md index d8195cf788..b3cb79beee 100644 --- a/handbook/engineering/README.md +++ b/handbook/engineering/README.md @@ -219,7 +219,7 @@ This workflow lets QA Wolf focus on test implementation while Fleet QA stays acc ### Prepare Fleet release -See the ["Releasing Fleet" contributor guide](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/releasing-fleet.md). +See the ["Releasing Fleet" contributor guide](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/workflows/releasing-fleet.md). ### Prepare fleetd agent release @@ -578,13 +578,13 @@ To generate a new page, you'll need: > Note: If this is your first time running the website locally, you will need to run `npm install` inside of the website/ folder to install the website's dependencies. -2. Call the `landing-page` generator by running `node ./node_modules/sails/bin/sails generate landing-page [page-name]`, replacing `[page-name]` with the kebab-cased name (words seperated by dashes `-`) of your page. +2. Call the `landing-page` generator by running `node ./node_modules/sails/bin/sails generate landing-page [page-name]`, replacing `[page-name]` with the kebab-cased name (words separated by dashes `-`) of your page. 3. After the files have been generated, you'll need to manually update the website's routes. To do this, copy and paste the generated route for the new page to the "Imagine" section of `website/config/routes.js`. 4. Next you need to update the stylesheets so that the page can inherit the correct styles. To do this, copy and paste the generated import statement to the "Imagine" section of `website/assets/styles/importer.less`. -5. Start the website by running `node ./node_modules/sails/bin/sails lift` (or `sails lift` if you have Sails installed globally). The new landing page will be availible at `http://localhost:1337/imagine/{page-name}`. +5. Start the website by running `node ./node_modules/sails/bin/sails lift` (or `sails lift` if you have Sails installed globally). The new landing page will be available at `http://localhost:1337/imagine/{page-name}`. 6. Replace the lorum ipsum and placeholder images on the generated page with the page's real content, and add a meta description and title by changing the `pageTitleForMeta` and `pageDescriptionForMeta in the page's `locals` in `website/config/routes.js`. --> diff --git a/handbook/finance/README.md b/handbook/finance/README.md index 4639824c2e..79c33146f4 100644 --- a/handbook/finance/README.md +++ b/handbook/finance/README.md @@ -107,7 +107,7 @@ Use the following steps to update the [💸Finance department KPIs](https://docs - Send the CEO a Slack DM with the balance of each of Fleet's two bank accounts. **Days to invoice customer**: -- Check the [invoice sent and payment received report]((https://fleetdm.lightning.force.com/lightning/r/Report/00O4x000007chpzEAA/view?queryScope=userFolders)) in Salesforce. +- Check the [invoice sent and payment received report](https://fleetdm.lightning.force.com/lightning/r/Report/00O4x000007chpzEAA/view?queryScope=userFolders) in Salesforce. - Sort by close date, then check invoice dates for any recently closed deals and enter them in the finance spreadsheet and create new rows at the top of the 'time-to-invoice' tab in the spreadsheet for each new entry. If a company has not been invoiced yet (invoice date is blank) do not enter yet, but verify if an invoice is scheduled to be sent using the [Invoice status and upcoming bill dates](https://fleetdm.lightning.force.com/lightning/r/Report/00OUG0000010r8b2AA/view) report. If it doesn't appear here, create an issue on the finance board to investigate. - Open the ["Time-to-invoice" tab](https://docs.google.com/spreadsheets/d/1lp3OugxfPfMjAgQWRi_rbyL_3opILq-duHmlng_pwyo/edit#gid=1835263594) in the [💸 Finance metrics spreadsheet](https://docs.google.com/spreadsheets/d/1lp3OugxfPfMjAgQWRi_rbyL_3opILq-duHmlng_pwyo/edit#gid=0). Enter the year and month + customer name in column A, then the # of days between the close date and the invoice date in column B. After entering new entries you will probably have to adjust the formula in column D to include the new cells in the average and make sure the formula includes no further back than the last three months of invoices.