Document annual process for IMS setup, use, and teardown

[srabraham]

Tool says this is approximately his process each year:

• Set up new event
• Add street names
• Edit permissions; this has stages, I have ideas on how to simplify/automate but haven't done it

Permissions are something like:

• Off season: read/write for OODs, Council, NVO Rangers, etc. read-only for a couple of others, auditors
• Summer: read/write for DPW Rangers
• Pre-event: read/write for command
• Event: read/write for operators [+Green Dot Leads]

I'm going to write this up in more detail, probably in a Google Doc

next steps would include making software changes to manage permission changes over those annual phases, and to set an event as being active

[chaoticbear]

We might be able to script some part of it too to make it a little easier.

[chaoticbear]

Also cron tasks to adjust permissions with a set time-frame might be good. Unless there's another mechanism that deals with expiring permissions.