Skip to main content

5 posts tagged with "Update"

Update

View All Tags

Project Email Is Moving to Group Mail — What You Need to Know

· 6 min read
PSEC
Architecture Team

Effective: 11 May 2026 (decided at the May 2026 PSEC)

After a fair bit of back-and-forth at the May PSEC, we've made the call: PSEC is moving project email from CloudHQ shared labels to Google Groups. Three projects are already converted and running on the new system — K10, GE1, and K7. Historical emails for those projects have been loaded into their respective groups, so when you join a group you'll see the full project history from day one, not just emails from today onwards.

The rest of the active projects will roll over progressively. From today, please treat Group Mail as the default for project correspondence.

PRMKit.2 — May Update: My Time, Leave Management & Smarter Approvals

· 5 min read
PSEC
Architecture Team
SAIYU
Construction Team

PRMKit.2 receives its biggest update yet — a ground-up rebuild of how people track time, request leave, and approve work. Every change listed here is live in production.

Previous releases laid the groundwork. This one rewires the plumbing: unified personal dashboards, a complete leave lifecycle with audit trails, holiday-aware approval UIs, and hardened bulk operations that no longer buckle under load.

Website Dashboard & URL Shortener

· 3 min read
PSEC
Architecture Team
SAIYU
Construction Team

The internal Website dashboard now lives behind a sign-in, and a new URL Shortener has been added alongside it. Both share the same login — one 4-digit code, two pages, no separate accounts.

WHS Knowledge Base Restructured

· 2 min read
SAIYU
Construction Team

The WHS Knowledge Base has been rebuilt from the ground up — updated content, and a structure that matches how construction safety professionals actually work on site.

Revision Code Format Update — Switching to YYMM.Alpha

· 2 min read
SAIYU
Construction Team

We've made a global update to our document revision code format across all PSEC × SAIYU documentation. This change was driven by a practical need for better readability, particularly within Fieldwire where long identifiers reduce clarity in tight UI fields.