Thanks, let me try to come up with a graphical view, but let me start with this verbal description. The permissions are no more complicated than having another resource on the page. The basic user/group permissions built into MODX are fine, which is why I would like to use them, and not have to duplicate anything.
A simple table structure would be a
Team_table (fields "id", "name", ...)
Roster_table (fields "id", "team_id", "player_name", "class", ...)
Schedule_table (fields "id", "team_id", "date", "time", "location", "opponent", ...)
I could add user_id to the team_table, but then I would have to do checks on this every call.
Here is a more visual example of the Front End of what I am talking about....
http://johnscreekgladiators.com/ It is a high school Athletic website. Imagine 10 sports, some with boys and girls teams. So about 20 teams. That means 20 logins or users, each with access to there own teams pages. I am thinking a context because some what to have there own vanity URL to go right to football like
http://www.gladiatorgridiron.com/
So the boys basketball would have a roster and a schedule and a calendar. now to make this a little more complicated they may have a Varsity team, JV and freshman teams. Each team has there own roster and schedule. But in the case of Boys Basketball they would all be managed by 1 account. - Lets ignore the groups for now.
There is probably a simple way to link these entries to a resource / context, so that I can use existing code and not have to duplicate existing functions. I am just not seeing it.
Thanks again for the replies.