Teams and permissions
A 200-user portal needs partitions, not a shared password.
Who may see a record is a design. Super-admin is not a role you hand to a new hire so they can get unstuck.
Team
Who shares an assignment pool and a set of records. A team is not a Slack channel pasted into a property.
Permission set
View, edit, delete, and export, named for a role. Write the set before the first user is invited.
Record access
Which deals, tickets, or objects a team may open. If the rule is everyone sees everything, write that down as a choice.
Check it
Open the view as a user who should not see the private deal. If they can, the filter is a wish.
The view
The filtered list people actually use. A saved view that shows the wrong records is a design failure, not a training issue.