Check what changed after each software release
Open the verified project, tell the assistant what changed and review the new boundary. Confirm a check of the partner role and compare evidence after the fix. Use monitoring available on your plan for its documented scope.
Prepare a post-release check →Partner portal change record
- Before: only staff could read invoices. Document the intended partner access.
- After: a partner may read assigned invoices only. Prepare assigned and unrelated fixtures.
- Decision: compare both reads after deployment and give any unexpected access to the developer.
Prepare the check with your AI assistant
Sample conversation
We added a partner portal after launch. Help me verify its new permissions against our existing customer accounts.
Assistant · Which partners are assigned to which invoices in this release? I’ll reuse the project’s verified target and propose controls for both assigned and unrelated invoices.
On first setup, verify the target and grant the assistant access to the intended project. Review the draft and confirm the run in your workspace.
Illustrative result and next action
A partner read an unassigned invoice. The developer added the assignment filter; the retest denied that invoice while preserving assigned access.
Questions before you start
Does dependency monitoring test my new role?
Dependency monitoring concerns known vulnerabilities in inventory. Describe new permissions and confirm a separate access check.
When should we rerun access checks?
After changes to roles, sharing links, integrations or export settings, describe the change and test the affected allowed and forbidden paths.
Where can the owner see changes?
Compare the original finding and retest in project history. Record the changed release and give the technical owner the expected rule.
Can I receive alerts without opening the report?
Review schedules available in your workspace and plan. In-app notifications and connected Telegram depend on the event and configured integration.
What can a public URL show?
An external check examines the reachable surface. Private workflows require authorized access and suitable test accounts. A source-code review or expert investigation has a different scope.
Can I reuse a prepared project?
Select the verified project, review the environment and permissions, then confirm the run. Recheck fixtures if the release changed the access model.