Differences

This shows you the differences between two versions of the page.

--- infrastructure:butterflymx [2025/12/27 06:24] – removed - external edit (Unknown date) 127.0.0.1
+++ infrastructure:butterflymx [2025/12/29 10:18] (current) – diamond
@@ Line 1: / Line 1: @@
+# ButterflyMX
+The building that dma.space is in uses ButterflyMX for their main entrance door access-control and paging system. Each board member maintains access to ButterflyMX directly through their individual accounts.
+## Passes
+ButterflyMX is able to generate a pass, with each pass containing multiple visitors. Its structure can roughly be understood as following:
+- Pass:
+  - Start time - when the pass becomes valid
+  - End time - when the pass becomes invalid
+  - Visitors:
+    - Name and Email - information about the visitor
+    - PIN code - the door PIN code for this visitor. Each visitor gets a different PIN code, even in the same pass.
+Note that the PIN code detail is very important: **prefer creating ONE pass for a single kind of access** (e.g. a "members" or "membership" pass), then for each person (e.g. member), add them as a visitor inside that pass. In other words, **think of a pass as an access group**. This will ease managing access by a lot.
+## Delivery Codes
+Letters and mail should be delivered fine, these will actually go straight to our inbox. But for packages, such as those coming from Amazon, special delivery access codes are required.
+**Do not create a Delivery Pass on the ButterflyMX app.** This code invalidates itself after a single use, so they're very infuriating for both you and the delivery person. Instead, prefer creating a recurring pass with valid access times during the day (e.g. Monday to Sunday, 8AM to 8PM), then clarify so in the delivery instructions. This way, you won't need to change them after every delivery.