You have been invited to a private network
GIK staff set up a network for Hurricane Odalys and invited your organization. You are not in it until you accept.
Hurricane Odalys — Gulf Coast
- Convened by
- GIK staff
- Disaster
- Hurricane Odalys
- Declared
- 2026-09-06
- Invited
- 4 organizations
Who is allowed to convene a network is Decision 3, and the board says nothing about it. Drawn here as GIK staff, which is the one candidate convener that already has a portal in this suite. If a supplier or a lead responder can convene one instead, this line changes and so does the permission model behind it.
Who else was invited
- Salvation Army — your organizationinvited
- Convoy of Hopeaccepted
- Gulf Coast Food Bankinvited
- Matthew 25 Ministriesdeclined
Your own row is the dark fill, not a tint — the wireframe standard keeps selection in greys so a reviewer does not read colour as product design. Whether an invited organization should see the rest of the roster before accepting is not on the board and is not in the spec; it is a real privacy question this screen surfaces by drawing one answer.
What this network is asking for
Pre-filled by the Hurricane template on the setup screen. Suppliers make inventory available against these lines from their own portal.
Join this network?
This is the step the board draws as its own state — "Members Join → Invite Accepted" — and it is what makes a network a thing an organization joins rather than a list someone keeps about it. Nothing in the platform today works this way: supplier-network-management models a standing roster the supplier alone controls, and the organizations on it need not know. Whether these two are one construct with two modes or two separate ones is Decision 1, and it gates the model.
Whether accepting also implies an agreement or MOU belongs to supplier-npo-agreements, not here. Illustrative placeholder data, in-memory state; accepting moves this page's own state and nothing else.