1
0
mirror of synced 2025-12-19 18:10:59 -05:00

Remove trailing spaces and blank line for linter (#57628)

This commit is contained in:
Felicity Chapman
2025-09-22 10:35:42 +01:00
committed by GitHub
parent 3dda7fffc3
commit d6230f36db
2 changed files with 3 additions and 4 deletions

View File

@@ -22,7 +22,6 @@ This feature is not enabled by default. An enterprise owner can enable the featu
1. Under {% octicon "gear" aria-hidden="true" aria-label="gear" %} **Settings**, click **Authentication security**.
1. In the "Enterprise access restrictions" section, select **Enable enterprise access restrictions**.
## Prerequisites
* You must use an {% data variables.enterprise.prodname_emu_enterprise %} on {% data variables.product.prodname_dotcom_the_website %}.
@@ -47,7 +46,7 @@ An enterprise owner can identify the correct enterprise ID to use in the header
{% data reusables.enterprise-accounts.settings-tab %}
1. Under {% octicon "gear" aria-hidden="true" aria-label="gear" %} **Settings**, click **Authentication security**.
1. In the "Enterprise access restrictions" section, find the header for your enterprise.
## Using the header
For best results, configure your proxy to inject the header into all traffic to the following **supported endpoints**.

View File

@@ -71,9 +71,9 @@ Now that you're happy with your app, let's deploy it so you can share it with ot
1. In the **Data Access** section of the publication dropdown, choose whether you want to give other users read-only or write access to your app.
Choose **read-only** to let others view your app, without allowing them to create, edit or delete content.
For example, if you've created a family calendar app and you want to showcase the app, but you don't want users to be able to create, edit or delete events in the calendar yet, choose **read-only**.
1. Click **View site** {% octicon "link-external" aria-hidden="true" aria-label="link-external" %} to see your deployed app, then copy and share your app's URL.
## Next steps