My assignments

Assignments is the answer to “what is on my plate today”. It sweeps every module for objects where you are the owner, the author, the assignee or the approver, and lays them out as one grid of buckets — so you stop opening eleven lists and filtering each by your own name.

Where to find it

Overview → Assignments in the sidebar.

What it collects

Each bucket shows a count badge and a compact table of the matching records. The rule that puts an object in a bucket differs by module, because “yours” means something different for a control than for an approval:

Bucket	What lands here
Applied controls	Controls where you are the owner
Tasks	Task templates assigned to you
Audits	Audits where you are listed in authors
Risk assessments	Risk assessments where you are listed in authors
Risk scenarios	Scenarios where you are the owner
Incidents	Incidents where you are one of the owners
Security exceptions	Exceptions where you are one of the owners
Follow-ups	Follow-up binders where you are an author
Findings	Findings where you are the owner
Validations	Validation steps waiting on you as approver
Risk acceptances	Submitted acceptances waiting on you as approver
Objectives (ISO)	Objectives assigned to you
Right requests	Privacy right requests where you are the owner
Metrics instances	Metric instances where you are the owner

The applied controls bucket keeps its status, priority and domain filters, so you can narrow a long action list to, say, everything P1 and still in progress without leaving the page.

An activity tracker sits at the top of the grid, summarising recent movement across your assignments so you can see whether the queue is shrinking.

Two toggles that change what you see

Include team assignments widens the sweep from you personally to every team you belong to. Turn it on when work is queued on a team rather than a named person — it is the difference between “nobody assigned this to me” and “nobody on my team has picked this up yet”. Press it again (it then reads Direct assignments only) to narrow back to your own name. The mode is carried in the URL, so a link preserves it.

Show empty sections reveals the buckets with a count of zero. By default they are hidden to keep the page scannable; reveal them when you want to confirm that you really have no open incidents rather than wonder whether the section is missing.

Note

Validations and risk acceptances are matched against your user account, not against a team, because an approval has to be attributable to a person. They stay on your list even when you are browsing in team mode.

Working the list

The counts load first and the tables fill in behind them, so a badge may appear a moment before its rows. Every row links to the object itself — open it, do the work, and it drops out of the bucket on the next load once you are no longer the one holding it.

A few habits keep the page honest:

• Set an owner on every applied control you create. An unowned control belongs to nobody’s list and quietly rots.
• Give tasks an assignee rather than relying on a shared mailbox — the bucket is driven by the assigned to field.
• Use Deprecated rather than deletion when a control is retired, so it leaves your queue without losing its audit history. See Applied controls.

Tip

Review dates live on the objects themselves — an applied control’s ETA, a task’s due date, a risk acceptance’s expiry date. Assignments surfaces the object; the date that makes it urgent is on the record. The calendar view plots the same deadlines by month if you prefer a time axis.

Related

• Analytics — the organization-wide counterpart to this personal view.
• Applied controls — where most assignments originate.
• Role assignments — who can see and act on what in the first place.