[thearche]

Summary

• Clarify that effective agent task permissions intersect with the scheduling user's permissions, not the agent creator's or permission-set administrator's rights.
• Explain the permission context after user intervention and the task-company scope.
• Show restrictions in both directions in the good/bad AL samples, document false-positive safeguards, and align the related default-access-controls article.
• Link the Microsoft Learn sources supporting the runtime behavior.

Why

Assigner is ambiguous and can lead reviewers to use the wrong user's permissions, treat grants as a union, or recommend widening agent permissions when the user-side grant is missing. The existing agents-domain article owns this concern; its BC 27+ applicability is unchanged.

Validation

• Knowledge frontmatter/structure validator: passed (0 errors; 2 existing keyword-count warnings in unrelated articles).
• git diff --check: passed.
• No compile task exists for these self-contained knowledge samples; they are not a deployable AL application.
• PowerShell fixture/contract checks were not run because PowerShell 7 is not installed.