docs: Document container type owner capabilities in SPE auth page#10751
docs: Document container type owner capabilities in SPE auth page#10751gnjoseph wants to merge 1 commit intoSharePoint:mainfrom
Conversation
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit eba7abc: ✅ Validation status: passed
For more details, please refer to the build report. |
gnjoseph
force-pushed
the
grjoseph/spe-auth-ct-owner-capabilities
branch
from
eba7abc to
875ea76
Compare
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 875ea76: ✅ Validation status: passed
For more details, please refer to the build report. |
gnjoseph
force-pushed
the
grjoseph/spe-auth-ct-owner-capabilities
branch
from
875ea76 to
a347add
Compare
|
Learn Build status updates of commit a347add: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
gnjoseph
force-pushed
the
grjoseph/spe-auth-ct-owner-capabilities
branch
from
a347add to
fc0d26f
Compare
|
Learn Build status updates of commit fc0d26f: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
docs/embedded/development/auth.md
Outdated
|
|
||
| [SharePoint Embedded Administrators](/entra/identity/role-based-access-control/permissions-reference#sharepoint-embedded-administrator) can manage all SharePoint Embedded applications created in the **owning** tenant. Additionally, any Microsoft Entra user that isn't an external identity can be assigned as an owner of a [container type](/graph/api/resources/filestoragecontainertype). Container type owners can manage that specific container type. To learn more about managing applications created in the owning tenant, see [SharePoint Embedded developer administrator](../administration/developer-admin/dev-admin.md). | ||
|
|
||
| ##### Container type owner capabilities |
There was a problem hiding this comment.
This was feedback given to me on this same article :)
docs/embedded/development/auth.md
Outdated
|
|
||
| ##### Container type owner capabilities | ||
|
|
||
| Container type owners are managed through the [permissions](/graph/api/filestoragecontainertype-post-permissions) navigation property on the `fileStorageContainerType` resource. Each permission entry has a role of `owner` and identifies the user via `grantedToV2`. Owners can be managed in the following ways: |
There was a problem hiding this comment.
nit. Generally, a resource name is bolded instead if it's not linked. So like fileStorageContainerType or fileStorageContainerType.
There was a problem hiding this comment.
Updated to be linked
- Add container type owner capabilities subsection under owning tenant management - Document permissions navigation property (roles: owner, grantedToV2) - Document owner CRUD, permissions management, and container creation capabilities - Add cross-tenant caveat: owners are NOT propagated to consuming tenants - Add intersection model callout (app permissions x user permissions) - Add auto-assignment of creator as owner and guest user exclusion
gnjoseph
force-pushed
the
grjoseph/spe-auth-ct-owner-capabilities
branch
from
fc0d26f to
8c33550
Compare
|
Learn Build status updates of commit 8c33550: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
2 participants
Category
What's in this Pull Request?
Documents the shipped container type owner capabilities in the SharePoint Embedded authentication and authorization page: