Introducing the New Sunrize Workspace

6 min read Sunrize Team

Sunrize went a while without a proper product update, and then we shipped a lot at once. The final batch landed over the last few days, but it represents a broader rebuild: a new application shell, new views, deeper organization context, and a clearer path from what is happening to what an administrator can do next.

The redesigned shell is the visible part. The larger change is how Sunrize organizes the work underneath it: When do local workdays overlap? Where is meeting load accumulating? What does a normal activity rhythm look like? Which people and departments are represented in the data? Can the useful parts come to us instead of waiting in a dashboard?

One workspace instead of a collection of reports

The first change is the most obvious one. Sunrize now has a consistent workspace with persistent navigation, a quieter visual system, clearer empty states, and layouts that hold together across organization and personal views.

It is easier to move from a high-level pattern to the people behind it, then into the settings and administrative history that explain how the workspace is configured. Sunrize also shows connected Slack and Microsoft 365 sources in context, so administrators can see what is contributing data without hunting through setup pages.

The new Sunrize People directory with department, region, timezone, and activity context
The People directory connects organization structure with timezone and recent activity context

Locations and timezones now answer operating questions

The rebuilt Locations & Timezones view goes beyond plotting where people are. It brings together timezone composition, local working hours, an overlap matrix, an approximate location map, and expected workforce coverage by hour.

Administrators can set the assumed local workday and project the results into the timezone they use for planning. Sunrize handles fractional offsets and changing timezone rules behind the scenes, while the interface stays focused on the practical question: when should enough of the organization be working for a handoff, launch, or support window to succeed?

Sunrize Locations and Timezones view with an overlap matrix and expected workforce coverage
Timezone overlap and expected workforce coverage are now part of the same planning view

Activity and calendar patterns have more context

Activity Analytics has been rebuilt around organization-level patterns. Summary measures, an activity heatmap, the typical activity rhythm, historical ranges, timezone controls, and detailed CSV exports now live in one clearer view.

The new Sunrize Activity Analytics workspace with summary metrics and an activity heatmap
Activity Analytics moves from summary measures into heatmaps, rhythms, and detailed records

Calendar Intelligence has grown as well. It now brings together scheduled meeting volume, meeting hours, people-hours, weekly patterns, invite responses, after-hours pressure, meeting sizes, external collaboration, and scheduled load by person or department. Activity and calendar data remain distinct signals, but they are much easier to read together.

The new organization-wide Calendar Intelligence overview with meeting totals, weekly patterns, and meeting sizes
Calendar Intelligence starts with an organization-wide view of meeting load and collaboration shape

The overview leads into the pressure behind those totals: participation outside local working hours, weekend meetings, short transitions, overlapping events, invitation responses, and the people or departments carrying the most scheduled load.

Sunrize Calendar Intelligence showing schedule pressure, invitation responses, and meeting load by person
Schedule pressure and invitation responses connect organization totals to the people experiencing them

People and administration are first-class parts of the product

The new People directory can be searched and filtered by status or organization group. Department, team, office, region, and timezone context can come from Microsoft 365 or a governed CSV import, making organization-wide views much more useful than a flat list of Slack accounts.

Individual activity profiles have also been modernized, including clearer timelines, summary statistics, and timezone-aware ranges. Organizations that enable personal dashboards can give employees a permission-controlled view of their own patterns.

Behind those views, Admin Activity records selected changes such as administrator access, organization-data imports, participation settings, personal dashboard access, and weekly roundup configuration. It is not a generic page-view log; it is a focused history of the actions that shape how Sunrize operates.

Weekly roundups bring the useful parts back to Slack

A dashboard is only useful when someone remembers to open it. Weekly admin roundups now bring a concise operating summary into Slack, including aggregate activity, expected workforce coverage, calendar metrics when Microsoft 365 is connected, and organization-data coverage.

Administrators choose the delivery day, time, and reporting timezone, and can send a test before turning the schedule on. The roundup goes to current dashboard administrators, putting shared context into the place where the next planning conversation is already happening.

Sunrize weekly administrator roundup scheduling controls
Weekly admin roundups can be scheduled and tested from Settings

What has not changed

Sunrize still builds its activity view from periodic workplace presence signals. It does not capture screens, read messages, inspect applications, or monitor keyboard activity. Calendar Intelligence analyzes scheduled event patterns and invite responses. The new workspace adds context and operational depth without changing that boundary.

The update is live now. Start free with Slack to explore the new workspace, or contact us to shape Sunrize around the systems, policies, and reporting needs of your organization.

Put the ideas to work

See how work really happens across your organization

Start with Slack and turn distributed-work patterns into practical operating context

Start free with Slack