Not everyone fits a role bundle exactly. With a permission override you change the permissions of one person in individual features of CIRO NOISE, without having to create a new bundle for them.
You set overrides under Organization › Members on the person's entry. There you see which features differ from the role, and Reset to role values removes all overrides at once.
How permission overrides work in CIRO NOISE
CIRO NOISE only stores what actually differs from the role bundle. If you set a feature back to the same value as the bundle, the override disappears. Every other feature stays tied to the bundle and changes with it. If the person switches to another bundle, their overrides stay in place.
Owners and admins set overrides. Every change is written to the organization's audit log, and the person concerned gets a notification that their permissions have changed.
Limits of an override
Overrides only exist for members with a role bundle. Owners and admins always have full access, viewers only read, and overrides have no effect on those roles.
An override also can't get past a limit set elsewhere. A time-tracking seat stays self-service, a switched-off feature stays off, and a finer permission such as financial figures only works if the person can at least read the feature it belongs to.
When you remove the person from the organization, CIRO NOISE deletes their overrides too. If they come back later, they start again with the plain values of their role bundle.
An everyday example
Four people work in an online shop's customer service with the Customer service bundle. Only Lena also handles credit notes and needs read access to Finance for that. The admin gives her an override for Finance, and the other three stay unchanged. When Lena moves to another team, he resets her to the role values in one click.