Changes that wait for a second admin
Agents cannot get around a rule, but an admin can change it. So Noset follows one principle: making things safer goes live at once, making them looser waits for a second admin.
What waits
Section titled “What waits”| Change | Why it is looser |
|---|---|
| A rule set version that loosens a rule: Ask or Deny to Allow, fewer approvers, a changed or deleted pattern | Agents could do more without asking |
| Switching four eyes off | Whoever starts an agent could approve its requests |
| A looser default rule set, or a looser rule set for one agent | Agents could do more without asking |
| Template updates by hand (“apply stricter template updates at once” off) | Stricter template updates would wait instead of going live |
| A looser template update written by Noset | The template’s new version loosens a rule |
| Single sign-on no longer required | People of the verified domains could sign in with an email link again |
| Show approvers the agent’s reasons | Approvers would see summaries of what agents said |
| Bringing back an offboarded admin | An admin can change people, rules and settings |
Until a second admin approves, the old state stays in force.
If your organization has only one admin, looser changes go live at once, and the rule’s approver team is told.
Decide
Section titled “Decide”Changes that wait are under Approvals › Waiting › Admin changes, each with a Looser chip and why it waits. The count next to Approvals includes the changes you can decide.
- Approve change or Reject: any admin except the person who asked. Any admin decides a version Noset wrote for a template update.
- Withdraw: the person who asked.
A rule set switch for one agent also shows in the agent’s row under Agents, where another admin can decide it right there.
Every change, and who decided it, is in the audit log.