Skip to content

Commit 5a6a7d1

Browse files
jorluiseptorVesaJuvonen
authored andcommitted
Update add-in-permissions-in-sharepoint.md (SharePoint#747)
Fixing the scope table. The text was joined to the URI and was confusing.
1 parent 1e461bd commit 5a6a7d1

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

docs/sp-add-ins/add-in-permissions-in-sharepoint.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -53,12 +53,13 @@ SharePoint supports four different permission scopes within the content database
5353

5454
**Table 1. SharePoint add-in permission request scope URIs and descriptions**
5555

56-
|**Scope URI**|**Description**|
57-
|:-----|:-----|
58-
|tenancyhttp://sharepoint/content/tenant|The tenancy where the add-in is installed. Includes all children of this scope.|
59-
|site collectionhttp://sharepoint/content/sitecollection|The site collection where the add-in is installed. Includes all children of this scope.|
60-
|websitehttp://sharepoint/content/sitecollection/web|The website where the add-in is installed. Includes all children of this scope.|
61-
|listhttp://sharepoint/content/sitecollection/web/list|A single list in the website where the add-in is installed. When the user who installs the add-in is prompted to grant permissions, the dialog enables the user to select one list to which the add-in is granted permissions. If the add-in needs permission to more than one list, it must request permission to web scope. Also, since you, the developer, have no way to control which list the user chooses or to tell the user which one to choose, you must use web scope if there is a list to which your add-in *must* have permission. (But there is a way to narrow the user's choice to certain subsets of lists. See [Permission request scope with associated properties](#AssociatedProperties) below.)|
56+
|**Scope**|**Scope URI**|**Description**|
57+
|:-----|:-----|:-----|
58+
|Tenancy| http://sharepoint/content/tenant|The tenancy where the add-in is installed. Includes all children of this scope.|
59+
|Site Collection| http://sharepoint/content/sitecollection|The site collection where the add-in is installed. Includes all children of this scope.|
60+
|Website| http://sharepoint/content/sitecollection/web|The website where the add-in is installed. Includes all children of this scope.|
61+
|List| http://sharepoint/content/sitecollection/web/list|A single list in the website where the add-in is installed. When the user who installs the add-in is prompted to grant permissions, the dialog enables the user to select one list to which the add-in is granted permissions. If the add-in needs permission to more than one list, it must request permission to web scope. Also, since you, the developer, have no way to control which list the user chooses or to tell the user which one to choose, you must use web scope if there is a list to which your add-in *must* have permission. (But there is a way to narrow the user's choice to certain subsets of lists. See [Permission request scope with associated properties](#AssociatedProperties) below.)|
62+
6263
If an add-in is granted permission to one of the scopes, the permission applies to all children of the scope. For example, if an add-in is granted permission to a website, the add-in is also granted permission to each list that is contained in the website, and all list items that are in each list.
6364

6465

0 commit comments

Comments
 (0)