Notifications, Audit, and Security
What Are Notifications, Audit, and Security
This chapter covers Budget alert notifications, audit-log searches, and personal-account and enterprise-level security settings. These capabilities provide warnings before an issue occurs and trace every key operation afterward.
Why Notification, Audit, and Security Mechanisms Are Required
Alerts notify relevant people before a limit becomes insufficient. Audit logs record who did what and when, supporting security investigations and compliance audits. Sign-in and verification policies reduce the risk of account takeover at the source.
How to Configure Notifications, Audit, and Security
Configure Budget Alerts
Budget alerts notify relevant people when Available Limit falls to a configured condition. Alerts do not increase the Budget automatically; an authorized person must review transactions and adjust the limit.
View Audit Logs
Audit logs record key operations, operators, objects, times, and results. When handling a permission or security event, filter by date, operation type, and object first, then open the details to verify the context.
Personal Account and Enterprise Security Policies
The personal-account page manages your password, identity, and verification methods. Enterprise security settings define sign-in requirements for the organization. They work together: when the organization enables a 2FA policy, each member must still bind 2FA to their own account.
Recommendation Enforce 2FA at minimum for administrators, finance staff, and developers. When someone leaves or changes roles, immediately update the account and role, and review API Keys, OAuth applications, and IP allowlists.