How can Actors be organized using generalization in Use Case Diagrams?

A child actor inherits all the use cases its parent actor can reach, then adds its own — so a specialised role gets the general role's access plus extra.

Actor generalization is about roles and the access they grant. You draw an arrow from the child (specialised) actor to the parent (general) one, and the child automatically connects to every use case the parent connects to:

        User (general)
       /     |      \
    Clerk  Administrator  Internet-User

• "User" reaches the basic functions
• "Clerk" (a User) reaches User's functions plus clerk-specific ones
• "Administrator" (a User) reaches User's functions plus admin ones

Why it matters: it removes redundant lines in the diagram, but for security it also makes the privilege hierarchy explicit — Administrator inherits every User capability, so any flaw in a User-level use case is also reachable by every higher role.

Contrast with use-case generalization (next card): here it's the actor (who) that's being specialised; there it's the use case (what) — same arrow notation, different thing being refined.