Use integrity and feature settings
To use integrity and feature settings, start with a signed-in account and a documented reason for the security or governance task. In Admin, review integrity finding, run supported corrective action, review feature setting, and change approved feature setting. Use the least access needed, verify the subject and scope, and keep secrets and personal data out of notes and support evidence.
Before you start
- A signed-in account and a documented reason for the security or governance task
- Verify actor, scope, time, and requested access before making or approving a change
Handle an integrity finding
- Open /admin/integrity with admin.admin and select one finding.
- Review its evidence, run only its exposed corrective action once, and verify the returned and audited status.
Change a restricted feature setting
- Open /admin/settings with approved scope and record the current value.
- Change one approved setting, save once, and verify its status or audit evidence; stop when approval or target scope is unclear.
Expected result
A supported integrity correction or approved feature-setting change returns an explicit status and preserved evidence. The two admin.admin routes remain separate, and an unclear scope or missing approval blocks the change.
Permissions
- Integrity and Feature Settings require admin.admin; documented approval, audit evidence, and target scope remain mandatory for changes.
Troubleshooting
An integrity action or feature setting is unavailable.
Confirm admin.admin, the correct route, documented approval, and exact target. Do not bypass the guard or substitute another control; record the finding or setting reference and visible status.
A corrective action or setting change has no final evidence.
Do not repeat it until the page status and audit evidence are checked. Escalate the route, target, prior and intended values or action, approval reference, returned status, and time.
Related articles
Enroll the signed-in user’s trusted authenticator without exposing the QR secret or one-time code.Manage personal privacy data
Request the signed-in person’s data export or account deletion once and track the returned status.Review audit and communication history
Filter and preserve scoped audit or communication evidence without treating the history as editable data.
Open in TajerGo
Sign in with the appropriate role and confirm your Business Account and branch before continuing.
Read as Markdown · Guidance for support agents
Last reviewed 2026-09-06 · Send documentation feedback