Simulating and reviewing a rule

Use the simulation and the final summary to confirm a data rule's effect before saving it.

When to use this

• Use it before creating a new rule.
• Use it before widening existing access.
• Use it when the rule involves a mask, a filter, or an expiry.

Before you start

• Fill in who receives the access, the data, and the rule's protections.
• Be clear about the result you expect.
• Check the user, group, catalog, schema, and table names.

Step by step

1. In the rule wizard, go on to the simulation or review step.
2. Check who will receive the access.
3. Check which data goes into the rule.
4. Check the expiry, masks, and filters.
5. Read the warnings the interface shows.
6. Go back to correct anything before saving.
7. Save only when the summary is correct.

What happens next

• The saved rule goes into propagation.
• The action is recorded in the audit trail.
• If the effect is not what you expected, edit or remove the rule.

Common errors

• Ignoring broad-access warnings.
• Saving it for the wrong group.
• Forgetting the expiry on temporary access.

Good practice

• Treat the final summary as an approval step.
• Ask for a second review on sensitive rules.
• Use the simulation whenever you change an important rule.

Next steps

• Editing or removing a rule
• Using row filters
• Glossary