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

Permission set 1001 "LOCAL"

Base Application · System.Security.AccessControl

Across versions

  1. BC23-30present

Neighbourhood 5 connected objects and pages

Permission set extension 4815 "LOCAL - Intr. Core" (extended by)LOCAL - Intr. CorePermission set extension 5012 "LOCAL - Serv. Decl." (extended by)LOCAL - Serv. Decl.Permission set extension 5265 "LOCAL - Audit Export" (extended by)LOCAL - Audit ExportPermission set extension 5285 "LOCAL - SAF-T" (extended by)LOCAL - SAF-TPermission set extension 693 "LOCAL - Paym. Prac." (extended by)LOCAL - Paym. Prac.

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.

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

Properties

Property Value
Access Public

Extended by

Recent changes

Countries that replace it

AT, AU, BE, CA, CH, DE, ES, FI, FR, GB, IS, IT, MX, NL, NO, NZ, RU, SE, US

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). 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: "permissionset", object_name: "LOCAL"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources