pageAdministration & Setupofficial - Microsoftderived - from the source, no model text

Page 9869 "Security Group Members"

System Application · System.Security.AccessControl

Across versions

  1. BC23-30present

Neighbourhood 4 connected objects and pages

Table 9021 "Security Group Member Buffer" (relates to)Security Group Member BufferCodeunit 9031 "Security Group" (calls)Security GroupControl Access Using Security Groups (Learn pages)Control Access Using Securit…Manage permissions through user groups (legacy) (Learn pages)Manage permissions through u…

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

System Application · System.Security.AccessControl · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Security Group Members
SourceTable Security Group Member Buffer
PageType List

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
Group User Name User Name Specifies the name of the user.
Full Name User Full Name Specifies the full name of the user.
Security Group Code Security Group Code Specifies a security group.

Triggers

OnOpenPage

Relations

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Documented on Microsoft Learn

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "Security Group Members"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 3 sources