Teams at workInspect and containExample · 1 question · 2 min

Find the Dangerous Permission

Trace inherited roles and find the permission that breaks the declared least-access rule.

Answer
Feedback
Finish

Your example

Mina's effective access

Mina has invoice read directly. The Finance Support group grants vendor-bank edit. Her role is invoice reviewer.

Show data as a table

Node	Details
Mina	role: invoice review
Finance Support group	Mina is a member
Invoices and totals	read · granted directly
Vendor bank details	edit · inherited from group

Choose one answer

Mina reviews invoices but inherits vendor-bank editing through a group. What should be removed?

Her direct right to read invoices and invoice totals.The inherited right to edit vendor bank details.

Show a hint

Compare each effective permission with Mina’s stated job.

About this activity

What you practise: Read a permission graph, distinguish inheritance from direct grants, and choose a narrow repair.

A hand-written example with a fixed sequence. It shows what working on a Klarisma activity feels like; your own activities follow your goals and material.

An example with fictional data. Your answers stay on this page and are cleared when you restart or leave.

Mina reviews invoices but inherits vendor-bank editing through a group. What should be removed? Mina has invoice read directly. The Finance Support group grants vendor-bank edit. Her role is invoice reviewer. Invoice review needs reading, not changing vendor payment details. The inherited edit right creates unnecessary, high-impact access.