Best practices
A little review of the AI Guide goes a long way. These habits help STYD give more accurate answers over time.
Practical habits
Review important tables first
Start with the tables used most for reporting and operations.
Start with the tables used most for reporting and operations.
Write clear descriptions
Explain unclear table and column names in plain business language, which rows count, the unit of an amount, what a status means, and save them.
Explain unclear table and column names in plain business language, which rows count, the unit of an amount, what a status means, and save them.
Add your business terms
On the Brief your assistant page, add the words your team uses and what they mean.
On the Brief your assistant page, add the words your team uses and what they mean.
Hide what should not be used
Hide irrelevant or sensitive tables, including from specific members where appropriate.
Hide irrelevant or sensitive tables, including from specific members where appropriate.
Confirm PII on sensitive columns
Make sure personal-information columns are flagged.
Make sure personal-information columns are flagged.
Refresh after schema changes
Run the analysis again when tables or columns change, your confirmed edits are kept. It costs prompts after the first analysis, and STYD shows the price first.
Run the analysis again when tables or columns change, your confirmed edits are kept. It costs prompts after the first analysis, and STYD shows the price first.
Keep security at the database
AI Guide visibility is an extra layer, not a replacement for database permissions. Keep using a read-only database user with access only to what STYD needs.
Combine with feedback and learning
Validate important answers, give feedback when something is wrong, and use the Brief your assistant page to capture the words your team uses. The AI Guide plus reviewed learning is what makes answers steadily more reliable.