Skip to content

Commit 762cb7e

Browse files
committed
Merge branch 'master' of https://github.com/SharePoint/sp-dev-docs into update-readme-relnotes
2 parents 1e66975 + 9282997 commit 762cb7e

12 files changed

+101
-21
lines changed

README.md

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,6 @@ This repository contains the raw documents published to docs.microsoft.com site.
1010

1111
Feel free to use [Issues]((https://github.com/SharePoint/sp-dev-docs/issues)) list to report us potential issues around the SharePoint Framework or gaps in our documentation. You can also submit directly pull requests towards our documentation.
1212

13-
We’ll also monitor [#spfx](http://sharepoint.stackexchange.com/tags/spfx/), [#spfx-webparts](http://sharepoint.stackexchange.com/tags/spfx-webparts/), and [#spfx-tooling](http://sharepoint.stackexchange.com/tags/spfx-tooling/) at [SharePoint StackExchange](http://sharepoint.stackexchange.com/) as well.
14-
1513
You can also tweet / follow [@Microsoft365Dev](https://twitter.com/Microsoft365Dev) or [@m365pnp](https://twitter.com/m365pnp).
1614

1715
## SharePoint Framework Releases
@@ -52,14 +50,9 @@ To keep track of improvements to the Office 365 Framework, please take a look at
5250
Provide Feedback:
5351

5452
* If you find issues or have new ideas and suggestions for SharePoint Framework, make sure you submit them [here](https://github.com/SharePoint/sp-dev-docs/issues).
55-
* [SharePoint StackExchange](http://sharepoint.stackexchange.com/) (please use [#spfx](http://sharepoint.stackexchange.com/tags/spfx/), [#spfx-webparts](http://sharepoint.stackexchange.com/tags/spfx-webparts/), and [#spfx-tooling](http://sharepoint.stackexchange.com/tags/spfx-tooling/) tags)
5653
* [SharePoint Developer](https://techcommunity.microsoft.com/t5/SharePoint-Developer/bd-p/SharePointDev) group at Microsoft Tech Community
5754
* [SharePoint Developer UserVoice](https://sharepoint.uservoice.com/forums/329220-sharepoint-dev-platform)
5855

59-
## Deployment Status
60-
The SharePoint Framework is now generally available at Office 365.
61-
62-
- [SharePoint Framework reaches general availability—build and deploy engaging web parts today](https://blogs.office.com/2017/02/23/sharepoint-framework-reaches-general-availability-build-and-deploy-engaging-web-parts-today/)
6356

6457
## Contribute on the SharePoint Dev Docs
6558

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
---
2+
title: Manage list item and file permissions with Power Automate
3+
ms.date: 07/16/2020
4+
---
5+
6+
# Manage list item and file permissions with Power Automate flows
7+
SharePoint connector in Power Automate provides the following actions to manage permissions of an individual list item in a list or a file in a document library.
8+
- Grant access to an item or a folder
9+
- Create sharing link for a file or folder
10+
- Stop sharing an item or a file
11+
12+
All of the above actions let you customize permissions for the item or a file to allow the right users to access that item or the file. To grant access or stop sharing, you will need to be a list owner of that list or library. That means, in your flow for these actions, you must connect to the list or library using a list owner user account.
13+
14+
## Grant access to an item or a folder
15+
The 'Grant access to an item or a folder' action requires the following inputs:
16+
- SharePoint site URL
17+
- List or library name or identifier
18+
- The item or the file identifier for which to grant access
19+
- The recipients whom you want to grant access
20+
- The permission role you want to grant
21+
22+
![Grant access to an item or a folder](../../../images/grant-access-item-file-action-flow.png)
23+
24+
In the flow action, you can also include a message and choose to notify the recipients once they get access to the item or the file.
25+
26+
> [!NOTE]
27+
> 'Grant access to an item or a folder' does not support granting access to external users.
28+
29+
### Choosing a permission role to grant access
30+
Depending on the user, you may want to grant them either access to edit or read. You can choose the right access in the Roles property.
31+
32+
![Choose the right role to grant access to an item or a file](../../../images/grant-access-item-file-roles-flow.png)
33+
34+
The permission roles map to [simplified standard SharePoint permission groups](https://docs.microsoft.com/sharepoint/modern-experience-sharing-permissions):
35+
- Members
36+
- Owners
37+
38+
### Using custom-defined roles to grant access
39+
In advanced scenarios where you need to specify a custom-defined permission role, you can do so in the flow action by entering a custom value for the *Roles* property in the following format:
40+
```
41+
role:<role-id>
42+
```
43+
44+
![Use a custom role to grant access to an item or a file](../../../images/grant-access-item-file-custom-role-flow.png)
45+
46+
If you want to get the role id for the custom-defined role permission, you can do so by navigating to the SharePoint URL in your web browser and then search for that role.
47+
```
48+
https://<your-sharepoint-site>/_api/web/roledefinitions
49+
```
50+
51+
For example:
52+
```
53+
https://contoso.microsoft.com/teams/itweb/_api/web/roledefinitions
54+
```
55+
56+
You can find the role Id in the *category* property of an role item.
57+
58+
![SharePoint site role definitions](../../../images/sp-web-roledefinitions.png)
59+
60+
## Grant access using sharing links
61+
Instead of granting users access to files directly, you can provide access to a specific file using [shareable links](https://docs.microsoft.com/sharepoint/modern-experience-sharing-permissions#sharable-links).
62+
63+
You can use the '[Create sharing link for a file or folder](https://docs.microsoft.com/sharepoint/dev/business-apps/power-automate/sharepoint-connector-actions-triggers#create-sharing-link-for-a-file-or-folder)' action to create shareable links for a given file.
64+
65+
> [!NOTE]
66+
> 'Create sharing link for a file or folder' only supports files or folders in a document library. List items are not supported yet.
67+
68+
![Create sharing link for a file or folder flow action](../../../images/create-sharing-link-file-action-flow.png)
69+
70+
When creating a shareable link using the action, you can specify:
71+
- Link type
72+
- Type of sharing link - view and edit or view only
73+
- Link scope
74+
- Who gets access to the link - anyone with the link, including anonymous or people in your organization
75+
76+
## Stop sharing an item or a file
77+
The 'Stop sharing an item or a file' action requires the following inputs:
78+
- SharePoint site address
79+
- List or library name or identifier
80+
- The item or the file identifier for which to stop sharing
81+
82+
![Stop sharing an item or a file flow action](../../../images/stop-sharing-item-action-flow.png)
83+
84+
Applying this flow action will reset all permissions except on that item or the file except for site owners.

docs/business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -53,8 +53,7 @@ To learn more about building workflows using Power Automate in SharePoint, start
5353
Many people feel there are significant gaps between SharePoint Designer (classic) workflows and Power Automate flows, but the list is not long. Of course, there are some workarounds you should consider in your planning as you move from classic workflows to Power Automate flows.
5454

5555
- **30 day run limit for flows** – SharePoint Designer workflows can run endlessly, but flows have a 30 day lifespan. Getting beyond this limitation means your flow will need to call itself in a re-entrant way to restart the clock ticking.
56-
- **HTTP Connector** – Flow has an HTTP connector (as an action), but it is a Premium connector. If you use HTTP calls extensively, you may want to create a “service account” user with a Power Automate license and run these flows with that user account. This also will make it easier to manage the set of flows you consider "enterprise" flows.
57-
- **Custom permissions on list items** – While there is not a flow action to accomplish this, it is possible to do it with an HTTP call.
56+
- **HTTP Connector** – If you make calls to SharePoint's REST API, then you can use the ['Send HTTP Request to SharePoint'](../guidance/working-with-get-items-and-get-files.md) action available in the SharePoint connector. Flow also has a generic HTTP connector (as an action), but it is a Premium connector. If you use HTTP calls extensively, you may want to create a “service account” user with a Power Automate license and run these flows with that user account. This also will make it easier to manage the set of flows you consider "enterprise" flows.
5857
- **Reusable Flows** – Using some modular thinking, you can create a master flow which a flow per list or library can call to do the heavy lifting. (In some ways this is even preferable, as you can edit a flow which is used in many locations centrally.) Alternatively, you can use flow actions to discover all of the lists or libraries which match some criteria and run the flow on them all on a timer rather than based on events.
5958
- **Workflow history storage** – Flows maintain a history in the context of the flow itself in the Power Automate dashboard. If you need tracking in your sites, you can have the flow log information in a list you create.
6059
- **Impersonation** - In SharePoint 2010 workflows, you can add an impersonation step to act as a different user. This capability is not readily available in flows.
@@ -185,8 +184,8 @@ While the following lists show some of the most common workflow capabilities, Po
185184

186185
|Permissions management action |Sharepoint workflow |Power Automate flow |
187186
|:-------|:-------|:--------|
188-
| Grant access to an item or a folder | Yes | Yes, works only with Modern Permissions |
189-
| Stop sharing an item or a file | Yes | Yes, works only with Modern Permissions |
187+
| Grant access to an item or a folder | Yes | Yes |
188+
| Stop sharing an item or a file | Yes | Yes |
190189
| Create sharing link for a file or folder | Not available | Yes |
191190

192191
### Approval actions
Loading
Loading
Loading
Loading
129 KB
Loading
53.5 KB
Loading

docs/spfx/release-1.11.0.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: SharePoint Framework v1.11 release notes
33
description: Release notes for the SharePoint Framework v1.11 release
4-
ms.date: 07/16/2020
4+
ms.date: 07/17/2020
55
ms.prod: sharepoint
66
localization_priority: Priority
77
---
@@ -11,16 +11,16 @@ New in this release, support for additional attributes in the solution for enabl
1111

1212
**Released:** July 16, 2020
1313

14-
## Upgrading projects from v1.9.1 to v1.10
14+
## Upgrading projects from v1.10 to v1.11
1515

16-
1. In the project's **package.json** file, identify all SPFx v1.9.1 packages. For each SPFx package:
16+
1. In the project's **package.json** file, identify all SPFx v1.10 packages. For each SPFx package:
1717
1. Uninstall the existing v1.10 package:
1818

1919
```console
2020
npm uninstall @microsoft/{spfx-package-name}@1.10
2121
```
2222

23-
1. Install the refreshed v1.10 package:
23+
1. Install the refreshed v1.11 package:
2424

2525
```console
2626
npm install @microsoft/{spfx-package-name}@1.11 --save --save-exact
@@ -50,13 +50,13 @@ New in this release, support for additional attributes in the solution for enabl
5050

5151
## Changes and deprecations in this release
5252

53-
- Knockout option for the SharePoint Framework web parts scaffolding has been removed. You can still use knockout if you prefer to do so, but there's no default scaffolding for it.
54-
- We have removed Node version 8 support in this release - use version 10 for now. Node v12 is not yet supported with SharePoint Framework development.
55-
- We have removed support for system.js in the local workbench
53+
- **REMOVED**: Knockout web framework option when creating SharePoint Framework web parts. You can still use Knockout, but there's no default scaffolding for it.
54+
- **REMOVED**: Node.js v8 support. For more information on the most current recommended versions, see [Set up your SharePoint Framework development environment](set-up-your-development-environment.md).
55+
- **REMOVED**: Support for system.js in the local workbench.
5656

5757
> [!IMPORTANT]
5858
> We are planning to remove support of the local workbench within the upcoming releases of SharePoint Framework.
5959

6060
## Known issues and limitations
6161

62-
There are no known issues as such with this release. If you find any issues around the provided version, report them to our centralized SharePoint dev issues list at https://aka.ms/spfx-issues.
62+
There are no known issues as such with this release.

0 commit comments

Comments
 (0)