Page 9827 "Default Permission Set In Plan"
System Application · System.Azure.Identity
Across versions
- BC23-25present
- BC261 procedures removed
- BC27-30unchanged
Neighbourhood 1 connected objects and pages
System Application · System.Azure.Identity · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
| SourceTable | Default Permission Set In Plan |
| PageType | ListPart |
| Permissions | tabledata “Default Permission Set In Plan” = rimd |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| PermissionSet | Permission Set | Role ID | Specifies the ID of the permission set. |
| Description | Role Name | Specifies the description of the permission set. | |
| Company | FirstCompanyTok |
Specifies that the permission set will be assigned to the first company that a user with this permission set signs in to. | |
| Extension Name | App Name | Specifies the name of the extension that provides the permission set. | |
| Permission Scope | Scope | Specifies the scope of the permission set. |
Relations
- source table Table 9019 “Default Permission Set In Plan”
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Default Permission Set In Plan"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.