Key Access Schedules
What changed: client.community.key_schedules(), key_schedule(key_id) and set_key_schedule(key_id, windows) (sync and async) let you read and set when a key may open its gates, mirroring the new public API endpoints.
Where to find it: README > client.community — access schedules, and the AGENTS.md cheat sheet.
What you’ll see: Typed schedule objects with the windows parsed out. The write replaces the whole schedule, and an empty list removes every restriction. key_schedules().blocked collects keys denied at all times because a saved schedule is switched off — a fault rather than a working schedule, which saving repairs. descendant_key_count tells you how many member keys a change will affect before you make it, since a schedule on the community key cascades to everyone beneath it.
What you need to do: Upgrade to 0.4.0 (pip install -U nimbio-community-api). The server and public API this depends on are live. Nothing else changes; existing keys are unrestricted.
Who this affects: Customers, Community Managers