You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/declarative-customization/site-design-overview.md
+7-4Lines changed: 7 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -110,7 +110,7 @@ The following example is a script that has two top-level actions. First, it appl
110
110
111
111
Each action in a site script is specified by a **verb** value in the JSON. In the previous script, the first action is specified by the **applyTheme** verb. Next, the **createSPList** verb creates the list. Notice that the **createSPList** verb contains its own set of verbs that run additional actions on only the list.
112
112
113
-
Available actions include:
113
+
**Available actions include:**
114
114
115
115
- Creating a new list or library (or modifying the default one created with the site)
116
116
- Creating site columns, content types, and configuring other list settings
@@ -121,12 +121,13 @@ Available actions include:
121
121
- Triggering a Power Automate flow
122
122
- Installing a deployed solution from the app catalog
123
123
- Setting regional settings for the site
124
-
- Adding principals (users and groups) to SharePoint roles
125
-
- Setting external sharing capability for the site
124
+
- Adding principals (users and groups) to SharePoint roles**
125
+
- Setting external sharing capability for the site**
126
126
127
127
For a complete list of available actions and their parameters, see the [JSON schema](site-design-json-schema.md).
128
128
129
129
> [!NOTE]
130
+
> ** These actions are automatically blocked for channel sites
130
131
> For libraries and lists, use the PowerShell command [Get-SPOSiteScriptFromList](/powershell/module/sharepoint-online/Get-SPOSiteScriptFromList) to create the site script syntax from an existing SharePoint list.
131
132
132
133
Site scripts can be run again on the same site after provisioning. Site scripts are non-destructive, so when they run again, they ensure that the site matches the configuration in the script.
In the previous example, the **Add-SPOSiteScript** cmdlet or **CreateSiteScript** REST API returns a site script ID. This is used for the **SiteScripts** parameter in the subsequent call to the **Add-SPOSiteDesign** cmdlet or **CreateSiteDesign** REST API.
| WebTemplate 1 | 64 | Team site (with group creation disabled) |
236
-
| WebTemplate | 68 | Communication site template |
238
+
| WebTemplate | 68 | Communication site template |
239
+
237
240
238
241
239
242
For step-by-step information about creating a site template, see [Get started creating site templates](get-started-create-site-design.md).
0 commit comments