Have something to say?

Tell us how we could make the product more useful to you.

Planned

Building Data Overview, Filtering + Unified Company/People Cards

Problem Data is currently hard to get an overview of across buildings, and key information about a person or company is spread across multiple places in the UI. Goal Make it significantly easier to filter data in Senbee and ensure that all relevant information about a company and a person is collected directly on the Company card and People card. Description Following an internal UI workshop, we will implement improvements to create a clearer overview of data distributed across buildings. This includes a stronger filtering experience and consolidation of data into the Company and People cards, so that information about a person and their company is unified in one place (rooms, keys, desks, financials, etc.).

Tristan White About 1 month ago

Completed

Limited People

Problem Not all people in a building should have access to Senbee features, but we still need them represented for structure, ownership, and notes. Description Introduce a new “Limited People” type. Limited People can be created and assigned to a company and other dimensions, with name fields and internal notes. Limited People cannot log into MySenbee and cannot use Senbee functionality such as meeting booking, communication, newsletters, etc. Key behavior Can be assigned: company + other dimensions Can store: name + notes Cannot: log in, use MySenbee, meeting booking, communication, newsletters, etc. Upgrade and downgrade rule Upgrade: Limited People can be upgraded to normal People by adding an email address. No downgrade (default): Normal People cannot be downgraded back to Limited People, because external integrations typically depend on the email address as a stable identifier. Migration window (temporary exception) We can open a time-limited migration window where downgrading People to Limited People is allowed during an agreed period. This is feasible now because external integrations are not yet opened up, later this becomes risky. Acceptance criteria Admin can create Limited People with company, dimensions, name, notes. Limited People cannot authenticate or access MySenbee. UI clearly distinguishes Limited People from People. Upgrading requires entering email and converts the record to normal People. Downgrade is blocked by default. Feature flag or time-bounded configuration enables migration-window downgrade.

Tristan White About 1 month ago

Senbee Connect API

Summary We are building a complete, unified API layer for Senbee Connect. This API will expose structured endpoints across the entire platform, making it possible for customers, partners, and integrators to programmatically access and manipulate core Senbee data. Scope The API will support querying and data operations for: Customers and organisations People and identities Facilities, rooms, and spaces Custom databases and collections Operational and environmental data streams Billing and usage data Module configuration and metadata Key Features Consistent, well documented endpoint architecture OAuth2 based authentication and permission scoping Real time and asynchronous endpoints where appropriate Strong typing and validation Webhooks for change events (customers, facilities, access, etc.) Rate limiting and API keys for partners Backwards compatible versioning Outcome This API becomes the backbone for future integrations, partner solutions, automation workflows and third party tooling. It enables customers to build on top of Senbee Connect without relying on custom one offs or direct database interaction. Target Q2-3 release in sync with the Senbee Connect platform launch, with beta access for selected partners earlier.

Tristan White 3 months ago