Transaction Notification Rules

overview transaction notification rules let you control which transfers trigger a notification for your team rules apply at the workspace level and take effect across both incoming and outgoing once you add rules, each finalized transaction is evaluated against them in order, and notifications are either allowed or blocked based on the conditions you set this is especially useful for teams that handle high volumes of small onchain transfers and want to limit noise to only the transactions that are operationally significant how rules work each rule follows this structure if \[incoming / outgoing] transactions are \[over / under] $\[amount] , \[allow / block] the notifications you can add as many rules as you need rules stack, so you can combine conditions if a transaction doesn't match any rule, the notification is sent through by default setting up rules go to settings → notifications click add new rules (if no rules exist) or add new rule (to add to an existing set) set the direction, condition, amount, and action for the rule add additional rules if needed rules are saved automatically example configuration a common setup for teams that want to cut noise from small onchain transfers while staying informed about significant activity rule direction condition amount action rule #1 incoming under $1 block rule #2 outgoing over $50,000 allow this configuration suppresses notifications for incoming dust transactions under $1, and ensures the team is notified for any outgoing transfer above $50,000