graph TD
orgs --> people
orgs --> groups
people --> availability
people <-.-> groups
The “🙆♀️ people” table records all people or contacts (not necessarily members) that are or have been affiliated with an organization such as MAIA, HAIST, etc. As an example: Everyone that even submits a form to MAIA (such as a rejected membership application) automatically gets added to the “🙆♀️ people” table. This table contains info on everything from dietary restrictions, submitted forms, events they are attending, and more. The “🏝 availability” table is an updating table that is an extension listing the availability of “🙆♀️ people”.
The “👨👩👧👦 groups” table is a bit of a work in progress. They are similar to Discord tags in the sense that some of them just mark a particular user (ex: on_forkable means they are on our Forkable mealplan service) or to grant them access to particular slack channels, google calendars, the MAIA office space, etc. (ex: The admin or member groups) via automations.
Screenshot of the “🙆♀️ people” table
Screenshot of the “🏝 availability” table. Schema subject to change.
The “🙆♀️ people” table records all people or contacts (not necessarily members) that are or have been affiliated with an organization such as MAIA, HAIST, etc. As an example: Everyone that even submits a form to MAIA (such as a rejected membership application) automatically gets added to the “🙆♀️ people” table. This table contains info on everything from dietary restrictions, submitted forms, events they are attending, and more. The “🏝 availability” table is an updating table that is an extension listing the availability of “🙆♀️ people”.
The “🙆♀️ people” table links to many other tables to show what things they are affiliated with, ex: being attendees or points of contact for events, forms they have submitted, tasks they are assigned, and more.
The current groups of type “clearance_level”
Clearance levels are a special group that controls the particular permissions and access to resources a user has. As an example, anyone with the “member” clearance level should get access to the Member Google Calendar, the Office via key card, or other future accounts (such as AWS) we have yet to create. Automatic access/account creation has yet to be implemented. The only automation so far is granting office access.