Remove trailing spaces and blank line for linter (#57628)
This commit is contained in:
@@ -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. 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**.
|
1. In the "Enterprise access restrictions" section, select **Enable enterprise access restrictions**.
|
||||||
|
|
||||||
|
|
||||||
## Prerequisites
|
## Prerequisites
|
||||||
|
|
||||||
* You must use an {% data variables.enterprise.prodname_emu_enterprise %} on {% data variables.product.prodname_dotcom_the_website %}.
|
* 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 %}
|
{% data reusables.enterprise-accounts.settings-tab %}
|
||||||
1. Under {% octicon "gear" aria-hidden="true" aria-label="gear" %} **Settings**, click **Authentication security**.
|
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.
|
1. In the "Enterprise access restrictions" section, find the header for your enterprise.
|
||||||
|
|
||||||
## Using the header
|
## Using the header
|
||||||
|
|
||||||
For best results, configure your proxy to inject the header into all traffic to the following **supported endpoints**.
|
For best results, configure your proxy to inject the header into all traffic to the following **supported endpoints**.
|
||||||
|
|||||||
@@ -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.
|
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.
|
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**.
|
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.
|
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
|
## Next steps
|
||||||
|
|||||||
Reference in New Issue
Block a user