From 794444f8ba63f44a10447e1c6d74d4b4c791d45b Mon Sep 17 00:00:00 2001 From: Richard MacGregor Date: Thu, 13 Feb 2025 10:16:20 -0800 Subject: Document exclusive and exclusivity in PermissionController's Role.md LOW_COVERAGE_REASON=NON_CODE_ONLY Bug: 394842195 Flag: DOCS_ONLY Relnote: N/A Change-Id: Ib9df00f53834afefcf54ad9f0cbd57a023680cbf --- .../src/com/android/permissioncontroller/role/Role.md | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'PermissionController') diff --git a/PermissionController/src/com/android/permissioncontroller/role/Role.md b/PermissionController/src/com/android/permissioncontroller/role/Role.md index 255214495..8d995d557 100644 --- a/PermissionController/src/com/android/permissioncontroller/role/Role.md +++ b/PermissionController/src/com/android/permissioncontroller/role/Role.md @@ -56,6 +56,13 @@ receive short text messages, photos, videos, and more". For default apps, this s the default app detail page as a footer. This attribute is required if the role is `visible`. - `exclusive`: Whether the role is exclusive. If a role is exclusive, at most one application is allowed to be its holder. +- `exclusivity`: Whether the role is exclusive and what type of exclusivity behavior it has. A role +can have exclusivity of `none`, `user`, or `profileGroup`. + - `none`: Role allows multiple holders + - `user`: Role allows at most one holder within each user + - `profileGroup`: (SDK 36+ only, fallsback to `user` on lower SDK) Role allows at most one holder +within a profile group (e.g. full user and work +profile) - `fallBackToDefaultHolder`: Whether the role should fall back to the default holder. This attribute is optional and defaults to `false`. - `featureFlag`: Optional feature flag for the role be available, as the fully qualified name of -- cgit v1.2.3-59-g8ed1b